[747] in athena10
Re: Codifying policy and procedure for Athena10/debathena.
daemon@ATHENA.MIT.EDU (William Cattey)
Fri Dec 19 00:04:49 2008
In-Reply-To: <20081219025335.GK1271@vinegar-pot.mit.edu>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <6092B9E5-7456-43CB-9C4C-C2AA56F6510D@mit.edu>
Cc: athena10@mit.edu
Content-Transfer-Encoding: 7bit
From: William Cattey <wdc@MIT.EDU>
Date: Fri, 19 Dec 2008 00:04:02 -0500
To: Greg Price <price@mit.edu>
On Dec 18, 2008, at 9:53 PM, Greg Price wrote:
> 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.
When they send email to the debathena list, they include a line,
"Signed-off-by:" with their
full name. We pull that from the email submission when we check
stuff in.
>
>> 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.
That sounds like a good idea, but let's get buy-in from more than
just me before we do it.
> Greg
