ViewVC Help
View File | Revision Log | Show Annotations | Revision Graph | Root Listing
root/i-scream/projects/cms/documentation/minutes/minutes-20010108.txt
Revision: 1.2
Committed: Tue Jan 9 21:56:21 2001 UTC (23 years, 9 months ago) by pjm2
Content type: text/plain
Branch: MAIN
CVS Tags: PROJECT_COMPLETION, HEAD
Changes since 1.1: +1 -1 lines
Log Message:
Spelt 'millennium' properly ;-)

File Contents

# Content
1 Minutes of meeting 08/01/2001 @ 2pm
2 Location: UKC Computer Science Meeting Room
3
4 Present: ab11, ajm4, pjm2, tdb1
5 Absent: None
6
7 The meeting began in an enthusiastic manner, with all group
8 members eager to get on - not what you'd expect for the
9 first Monday of the Millennium!
10
11 First, a review of work done, if any, over the Christmas
12 break. Paul was first to state that the "historal clients"
13 he's been doing (web based) are a lot harder than they first
14 seemed, but they are coming along very well. Tim reported
15 that he had put a queue into the central point of the
16 server, and added a few features (eg. javadoc generation) to
17 the makefiles. Ash told the group about his work on the
18 host, and plans to restructure it to aid porting to C++.
19
20 AJ was pleased to report back that it had been lovely and
21 sunny in Teneriefe, in constrast to the snow in the UK, and
22 that he'd had some 'ideas'.... the group sighed :)
23
24 Initial discussions started with what needed to be done this
25 term, and when by. It was agreed that there were probably 10
26 weeks at the most to get everything finished, and everyone
27 was happy with the notion that it should be completed
28 *before* the start of project week. A target of around 5
29 weeks was set to complete the majority of the coding, giving
30 us the rest for documentation, testing and review. More
31 precise goals may be set in weeks to come.
32
33 AJ mentioned that a "text based" client could be useful, and
34 likened it to the "top" program found on raptor
35 (/usr/local/sbin/top). This would display basic information
36 in an easily digestable form, and would be quick to load.
37 This is something that the customer has requested.
38
39 AJ also brought up an idea suggested by Tim a while back,
40 the restructering of logging in the server. The idea was
41 that the log messages would be sent to a logging unit, as
42 they do at present, but that this logging unit would pump
43 these messages back into the filter system for delivery to
44 clients. This would remove the single logging console
45 (although it could still log to a file), and allow any
46 client to view the current status of the server.
47
48 This brought on the discussion of how these would pass "un-
49 filtered" through the system, which then led to the similar
50 issue with heartbeats. This would be looked into by Tim,
51 although no work would be done on the logging setup at this
52 stage. More emphasis was placed on making the server
53 'complete', which entails fixing the heartbeat problem.
54
55 Next it was decided what would be done in the immediate
56 future. Paul requested doing the command line client after
57 completion of the historical clients, which should be
58 completed in around a week. The group agreed on this.
59
60 AJ said he had ideas for a GUI client, and would work on
61 this. Ash said that a rewrite of the host was required to
62 make porting to C++ easier. He also said work on the C++
63 host was to begin soon.
64
65 Tim is to complete the functionality in the client interface
66 part of the server, and patch up other areas that needed
67 fixing (eg. heartbeats). The aim is to "complete" the server
68 at this stage.
69
70 Finally, it was pointed out that the server needs to be
71 brought to a stage where it can be released and set running
72 on raptor. This is required so the group members working on
73 hosts and clients can test their setup is complete.
74
75 The next meeting will be on Wednesday afternoon after the
76 meeting with Ian. Meeting room is booked 3pm to 5pm.