[743] in athena10

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

Codifying policy and procedure for Athena10/debathena.

daemon@ATHENA.MIT.EDU (William Cattey)
Thu Dec 18 18:03:08 2008

Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <5ABFA230-3440-43A0-9C22-23E54FE79088@mit.edu>
Content-Transfer-Encoding: 7bit
From: William Cattey <wdc@MIT.EDU>
Date: Thu, 18 Dec 2008 18:01:15 -0500
To: athena10@mit.edu

I have continued chatting with jdreed, tabbott, and amb on the issues  
of codifying the policy and procedure for dealing with submissions  
from non MIT folk into Athena 10 and debathena. I think we've come to  
closure on the following:

Outsiders will be instructed to join the debathena list, and to send  
patches there.  They will be pointed to submission guidelines that  
tabbott will put onto the debathena site, that echo the Linux "Signed- 
off-by" approach. Specifically outsiders will need to add a "Signed- 
off-by" line when they submit a patch.

Regular commits happen as they have been but when a committer here  
commits an oursider's patch, a "Signed-off-by" comment is added  
naming the outsider

This does create a possible point of confusion because we're using  
the "Signed-off-by"comment as an intellectual property audit trail  
rather than in its original intent to do that AND to sign off on the  
functionality.  It's probably ok to just remind ourselves that the  
committer in the SVN repository is the one who signed off on testing  
and functionality at MIT.  An alternative would be to just archive  
the debathena list and not make the "Signed-off-by" comment in the  
repository, but since SVN is our repository of record, it's probably  
safer to abuse the english language a bit, and to put the  
intellectual property audit there.

Going forward, debathena will be the primary list for technical  
discussions.  Athena10 will be a mix of technical and policy  
discussions as we deploy the debathena developments as IS&T supported  
products.  Release-Team will be for the nitty-gritty boring IS&T  
discussions that nobody should have to slog through  :-) .

-Bill

----
Important: IS&T IT staff will *NEVER* ask you for your password, nor  
will MIT send you email requesting your password information. Please  
continue to ignore any email messages that claim to require you to  
provide such information.
----

William Cattey
Linux Platform Coordinator
MIT Information Services & Technology

N42-040M, 617-253-0140, wdc@mit.edu
http://web.mit.edu/wdc/www/




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