/[i-scream]/projects/cms/documentation/minutes/minutes-20001122.txt
ViewVC logotype

Contents of /projects/cms/documentation/minutes/minutes-20001122.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph


Revision 1.1 - (show annotations)
Sat Nov 25 23:17:24 2000 UTC (18 years, 5 months ago) by tdb
Branch: MAIN
CVS Tags: PROJECT_COMPLETION, HEAD
File MIME type: text/plain
Minutes from the meeting on 22/11/2000.

1 Minutes of meeting 22/11/00 @ 3pm
2 Location: UKC Computer Science Meeting Room
3
4 Present: ab11, ajm4, pjm2, tdb1
5 Absent: None
6
7 The meeting was short due to a prior engagement at 4pm.
8
9 The group reviewed the current progress of the server and
10 produced a detailed diagram of the current state of the
11 system. This allowed the group to clearly identify the parts
12 that needed to be finished off, and familiarise everyone
13 with how things are fitting together.
14
15 AJ & Tim agreed to finish of parts of the Filter Manager,
16 and the Filter. This should all be completed for Monday.
17
18 Paul is to start some preparation work for the database part
19 of the system. He will look at how things fit together with
20 regard to Java, mySQL and PHP.
21
22 For information, here the details of our mySQL database
23 currently on raptor.
24
25 Database server: raptor.ukc.ac.uk
26 Database name: co600_10_db
27
28 Username: co600_10
29 Password: ...as if I'd put it on the website ?
30
31 To get started with the database the following command would
32 probably be quite useful;
33
34 mysql --database=co600_10_db -u co600_10 -p
35
36 A password will be prompted for.
37
38 Paul suggested that some time needs to be put into coming up
39 with a design for the database. This should be discussed
40 further at the next meeting.
41
42 Finally Ash said he should be able to have the Java host
43 ready for Monday.
44
45 The group agreed that Monday would be a good point in the
46 development process to have a code review session. This is
47 so that all group members are aware of the processes
48 involved in the whole system, and how it fits together. It
49 will also bring out issues such as coding standards and
50 design issues that should be consistent across all code.
51
52 The next meeting will be on Monday afternoon at 2pm. The
53 group concluded that the morning meeting was pointless due
54 to constant difficulties with people getting there, and
55 other commitments in the later parts of the morning.

  ViewVC Help
Powered by ViewVC 1.1.26