[6185] in SIPB bug reports
sipb-nonmem and prospectives with write bits on install volumes in sipb locker
daemon@ATHENA.MIT.EDU (Sam Hartman)
Mon Oct 21 22:28:42 1996
Date: Mon, 21 Oct 1996 22:27:40 -0400
From: Sam Hartman <hartmans@MIT.EDU>
To: bug-sipb@MIT.EDU, sipb-afsreq@MIT.EDU
Cc: jmorzins@MIT.EDU
Chad, in order to advance the SIPB locker reorganization, has
apparently decided to create a prefixless AFS group sipb-nonmem and
give certain proospectives write access to the new SIPB locker install
volumes. I formally object:
* SIPB traditionally does not allow prospectives to write to install
volumes in the SIPB locker. I know of cases (including myself) where
prospectives have been given write access to build in source volumes
for specific software packages. This is reasonable and should be
continued when appropriate. However, since SIPB supports the SIPB
locker there should be a member who actually installs the software and
checks to make sure proper build procedures were followed.
* If there are prospectives who have sufficient experience in release
engineering and software support that we want them maintaining
software in the SIPB locker without a member's help, there is a
process called membering that should be applied as the appropriate
access control mechanism.
* This really should have been discussed on bug-sipb, or at least with
several people in a public zephyr class.
* I think sipb-nonmem is a bad name for the group. It doesn't imply
that it has gsipbbin like access.
In Chad's defense, he indicated that this was a temporary
measure. I am unconvinced that this is necessary even as a temporary
measure.
--Sam
