[6193] in SIPB bug reports
Re: sipb-nonmem and prospectives with write bits on install volumes in sipb locker
daemon@ATHENA.MIT.EDU (Salvatore Valente)
Thu Oct 24 20:29:25 1996
Date: Thu, 24 Oct 1996 20:29:09 -0400
To: Sam Hartman <hartmans@MIT.EDU>
Cc: bug-sipb@MIT.EDU, jmorzins@MIT.EDU
In-Reply-To: "[6185] in SIPB bug reports"
From: Salvatore Valente <svalente@MIT.EDU>
Sam wrote:
<Sal gave> certain prospectives write access to the new SIPB
locker install... I formally object:
* SIPB traditionally does not allow prospectives to write to install
volumes in the SIPB locker...
...<more objections>
Objection overruled. :-)
As for the particular prospective added, jmorzins, I've only talked to
him once or twice, and have no idea if he's "qualified" to install
stuff. But I figure that if he's not, then I'll notice and fix things
and tell him what had to be fixed and then he'll be qualified.
We always say that prospectives should get involved in projects. A
couple of months ago, I sent out email asking anyone to become in the
new sipb locker project. Jacob's response was not only the first
response I got from a prospective; it was the only response I got at
all. I was thrilled to get it. I was happy to give him access to the
project.
(Yes, I realize that there are also security concerns with giving
nearly random people write access to a Sipb service locker. I chose
to ignore them because I figured that someone who wanted to install a
trojan horse in the Sipb locker wouldn't ask for permission to do
so...)
-Sal.
