[6203] in SIPB bug reports
Re: sipb-nonmem and prospectives with write bits on install volumes in sipb locker
daemon@ATHENA.MIT.EDU (Sam Hartman)
Wed Oct 30 18:13:06 1996
To: Salvatore Valente <svalente@MIT.EDU>
Cc: bug-sipb@MIT.EDU
From: Sam Hartman <hartmans@MIT.EDU>
Date: 30 Oct 1996 18:09:45 -0500
In-Reply-To: Salvatore Valente's message of Mon, 28 Oct 1996 18:56:15 -0500
>>>>> "Salvatore" == Salvatore Valente <svalente@MIT.EDU> writes:
Salvatore> Sam pointed out that I should have sent notification to
Salvatore> bug-sipb before giving a prospective write access to
Salvatore> the sipb-new locker. He's right that I should have
Salvatore> sent notification and asked for consensus, but I'm not
Salvatore> convinced that bug-sipb is the appropriate place.
Salvatore> Perhaps we should create a bug-new-sipb list (which
Salvatore> would go away if sipb-new ever actually replaces sipb)?
Sounds like a good idea to me. I can't find any SIPB spare
lists, so I won't deal now, but we should obtain some spare lists as
well as a bug-sipb-new list.
Salvatore> Sam also wrote:
Salvatore> I would much prefer if you had given him write access
Salvatore> to the source and build volumes, then installed stuff
Salvatore> when he said it was ready. I don't think this is much
Salvatore> extra work, and gives you a good chance to look at the
Salvatore> quality of the release engineering and maintainability
Salvatore> of his builds.
Salvatore> Again, I see your point but I'm not 100% convinced.
Salvatore> When any member or prospective is going to help
Salvatore> maintain the sipb locker, sooner or later he/she will
Salvatore> install his/her first program there. I think it's a
Salvatore> good idea for a person's first attempt to be in a
Salvatore> locker that's not actually used by most people, so we
Salvatore> have more time to catch mistakes.
Hmm; I was thinking more of sipb-new as something that would
soon become sipb. I guess so long as you have some member check over
the installed software before you promote it, this argument is
reasonable.
Salvatore> To put it an other way: At what point do you think we
Salvatore> should start trusting someone not to screw up?
Never. Seriously, I see your point.
Salvatore> -Sal.
