[746] in athena10

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

Re: Codifying policy and procedure for Athena10/debathena.

daemon@ATHENA.MIT.EDU (Greg Price)
Thu Dec 18 21:57:07 2008

Date: Thu, 18 Dec 2008 21:53:35 -0500
From: Greg Price <price@MIT.EDU>
To: William Cattey <wdc@mit.edu>
Cc: athena10@mit.edu
Message-ID: <20081219025335.GK1271@vinegar-pot.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5ABFA230-3440-43A0-9C22-23E54FE79088@mit.edu>

On Thu, Dec 18, 2008 at 06:01:15PM -0500, William Cattey wrote:
> 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

If the point is to get a commitment from the outsider that the patch
is licensed appropriately, you probably want them to add the
"Signed-off-by" themselves, or in some other way have them make that
clear.


> 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  :-) .

Perhaps we want to invert the mailing-list structure, then?  Currently
debathena@ is on athena10@ and not vice versa, so this proposal would
have the people on athena10@ miss the technical discussions while the
outsiders on debathena-listeners see the policy and IS&T discussions.

Greg

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