[222] in Project_DB
notes, 9/18
daemon@ATHENA.MIT.EDU (Mike Barker)
Tue Sep 23 15:09:17 1997
To: project-db@MIT.EDU
Date: Tue, 23 Sep 1997 15:09:09 EDT
From: Mike Barker <mbarker@MIT.EDU>
Attending: brlewis, mbarker, brendakg, tjm, wdc
Agenda:
1. v2 status
2. team leader off front page?
3. reporting problems
4. glossary
5. articles review
6. http://web.mit.edu/project-db/index.html
7. how to service and support
bits and pieces
1. v2 status
brl version is available
documentation, training, etc. falling short
(we think it would be great if the front page were tailorable
per person)
We would like project-db.mit.edu to point to arachne (Bruce sent mail
asking that this happen, and it was reported that it was done)
[note: I tried going to https://project-db.mit.edu/ and netscape told
me that someone might be spoofing because the site name and the
certificate didn't match up...this may not be such a good idea?]
[hum...my notes say this is where Bill started drawing on Bruce's
whiteboard. here's my notes on that:
project-db.mit.edu -> cname for arachne
http://project-db.mit.edu/ intro + "if you need R/W"
https://project-db.mit.edu/ intro page R/W pdb
Intro page
This is the Project db...
All Projects link
My projects link (Bruce will show me how to make this magic?)
Efforts by process links (discovery, delivery, ...)
What's in a Project DB Entry? (link)
What should you put into a Project DB Entry? (link)
Glossary
Tutorial
Reporting Problems (link)
---------------------------------------------------
We would like the front page (index, top level) to link to more info.
Action Plan:
Mike hashes up something
Tim and Brenda act as curmudgeonly reviewers of the something
2. team leader off front page?
postponed. see what Mike comes up with.
3. reporting problems
see #7, how to service and support
4. glossary
brenda will provide for Mike to mix into hash.
5. articles review
Tim read them and remembered doing so. Mike thought he read them,
but might have been dreaming. We all should read them.
6. http://web.mit.edu/project-db/index.html
see hash.
7. how to service and support
postponed to next meeting.
Next Meeting Schedule and Preliminary Agenda:
10/9
1. Action Item Review (want to bet mike forgets to put
potatoes in the hash?)
2. v3 discussion (including make/buy discussion)
3. how to service/support (probably somewhat mixed up with above)
Derivative Action Item: We (yes, this means you) should consider who
are appropriate participants in the service/support discussions and
whether we need to invite more people.
mike
