[89] in Project_DB
Amendment to Proposed Project DB changes.
daemon@ATHENA.MIT.EDU (Bill Cattey)
Sat Apr 12 23:43:36 1997
Date: Sat, 12 Apr 1997 23:43:23 -0400 (EDT)
From: Bill Cattey <wdc@MIT.EDU>
To: project-db@MIT.EDU, jis@MIT.EDU, nschmidt@MIT.EDU, itlt@MIT.EDU
I intended to send this out at the beginning of last week, but
I've been overwhelmed with job-search obligations.
After Miki reviewed it, I got sick and forgot to send it out.
Much delayed, here it is. Please respond to the project-db list if you
think this amendment IS or IS NOT ok.
-wdc
----
In the process of prototyping the changes we specified for allowing
a new group of people to have permission to create projects, Miki
encountered a problem. It turns out that if we use the "Formal
Committment" bit to differentiate projects, then it must be set
to either YES, or NO, and most of the projects currently existing
have no value set here.
So instead of using that bit, we are adding a new process
"NONE". (This was an optional part of the original proposal.)
So here is how things will work:
If the creator of a project is not a director, the Process will
be set to "NONE".
The non-director project creator will get automatically added to the
list of leaders for that particular project so that they will, in
future, be able to modify the project.
Projects with process "NONE" will appear separately from the other
projects.
Either a director or the users appearing in the list of leaders for the
particular project will be able to modify the process of the project to
set it to belong to a particular director.
The bottom line here is:
Everybody who could potentially lead a project will be empowered to
create projects, and to modify projects they lead. Both sets of
people can set the "Process" of the project.
The expectation is that projects under a particular process really
are owned by the respective process director, and that naming a process
for a particular project represents a formal level of committment. The
user interface is not presuming to enforce any particular policy here.
Right now directors and the particular project leaders can modify the
process of the project.
My personal hope here is that the project database serves as the
backbone for better communication between project leaders and directors.
-wdc
