[835] in athena10

home help back first fref pref prev next nref lref last post

Re: Merging Debathena and Athena 10

daemon@ATHENA.MIT.EDU (Jonathan Reed)
Tue Jan 13 17:21:14 2009

Cc: athena10@mit.edu
Message-Id: <0F457534-688D-4330-A642-78DBC2B815C9@mit.edu>
From: Jonathan Reed <jdreed@MIT.EDU>
To: Evan Broder <broder@mit.edu>
In-Reply-To: <496D0F4B.9010709@mit.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 13 Jan 2009 17:20:16 -0500

> One of the things that is key to SIPB for this to be a viable plan is
> that we don't completely lose all access to the apt repository.  
> However,
> IS&T is presumably concerned with non-payrolled (well, all of us  
> aren't
> on payroll) students being able to make changes to things like all the
> clusters, and IS&T may also not be happy with us having direct  
> access to
> linux-build-10.
>
> I think the best way to deal with this is twofold: (a) the list of  
> SIPB
> people who can contribute directly to Athena 10 should be kept short -
> probably 3 or 4 people at most.

This sounds perfectly reasonable as far as I am concerned.  I suspect  
most of IS&T's concerns can be mitigated by having a formal "process"  
by which one gets repository access.  Such a process would likely  
consist of coming to N42/W92, getting a copy of any policies and  
procedures we draw up, and signing something which states that users  
will abide by those policies, etc, etc.  If this sounds remarkably  
similar to the procedure to become an FSILG net contact, that's  
because it is.

-Jon

home help back first fref pref prev next nref lref last post