Documentation : Hardware | Software | Tutorials    Wardrobe : Jackets | Applications
Papers : Notes | Proposals | Research    Administration : Stock | Minutes | Progress

Jun 10th 1997

At 9.30am in David's office.
present: david, jim, paul, phil


1. Choose hardware platform and operating system for CyberJacket.

We reconsidered Java as an option. Advantages:

There are a few hurdles:

Java is the 'interesting' choice; after this we looked at the most expedient choices. These were Linux and QNX. For Linux we know that the kind of drivers we need are all available and that there is some student experience; also its free and there is a lot of user experience available informally from notes groups. QNX is of interest because of experience within Labs, but its not free and its generally less well known than Linux.

Other options such as WinCE were not discussed much, the assumption being that they were neither as 'interesting' as Java or as expedient as Linux.

For hardware we decided to go with the Epson card and motherboard as an expedient choice (we've already got one, and we have experience with it). Other options may be beefier and have lower power consumption, but it would take too long to check them out.

Summary: we will go for Java if possible, followed by Linux and then QNX if not. In all cases we will plan to use the Epson platform unless we are presented with a specific, obviously superior option.

Action: David and Paul (and Rupert and James) to approach Sun to guage their reaction and decide whether we can go with Java.

Action: Jim to understand why labs choose QNX over Linux.

Action: Jim, Phil and Peter Rodgers to get an Epson board over to students for examination.

2. Agree on partitioning of work between four students and on their supervision.

Jim's initial proposal was too ambitious. David was keen that we should specifically set time aside for testing to ensure that the cyberjacket was a robust platform for future work.

We devised the following proposal.

Selecting students for Summer '97

Action: Paul will take advice in order to pre-select students. He will then get CVs to Jim, who will drive the funding process at HP.

Students will be based at Bristol University. Jim and Phil will assume formal reviewing roles and as such will spend one morning a week with the students, but they will not have any day-to-day supervision responsibilities.

Action: Paul will find lab space for the students.

3. Introduce the web site. Decide whether to use FrontPage.

The univerity folks are mainly workstation-based, whereas FrontPage is a PC application. Currently the university folks enter HTML code directly using Vi, so they are open to considering a WYSIWIG solution even if it is PC-based.

Action: Jim to help Paul get a copy of FrontPage to try.

4. Distribute non-disclosure agreements to Henk and Paul.

Action: Jim to go through non-disclosure agreeements with someone familiar with them in order to prepare forms before transfer to Bristol Uni staff. Also to look into student non-disclosure arrangements.

5. Any other business.

David mentioned the importance of developing proposals for student projects for the fourth year. These could emerge at least partly by circulating a few of our earlier application ideas around students. In which case our thoughts need to be written up on this web.

We were introduced to Rupert Key and James Dobson - students interested in doing Summer work on the project. They talked about OS system requirements for the cyberjacket. They were especially interested in Java.

Action Summary

This page last updated June 27, 2002
The material displayed is provided 'as is'. Contents may not be reused without prior permission.
For problems or questions regarding this web contact Cliff Randell.