Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4A7C19F1.6040502@canonical.com>
Date: Fri, 07 Aug 2009 13:11:29 +0100
From: Elliot Murphy <elliot@canonical.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090804)
MIME-Version: 1.0
To: dev@couchdb.apache.org
Subject: Re: Uneasiness with use of github for experimentation
References: <399A2534-FBBB-4D0E-A7C9-A04AB0E175BA@apache.org>
 <96A8267B-72C4-473F-A78A-B8C665805D4A@gmail.com>
 <e2111bbb0908061145p59ca6925ka8ab506780d84198@mail.gmail.com>
 <EC2B169F-5900-434E-BBF9-9B91A194F36D@apache.org>
In-Reply-To: <EC2B169F-5900-434E-BBF9-9B91A194F36D@apache.org>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigA070154F2CE459D18FE26CCB"

--------------enigA070154F2CE459D18FE26CCB
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 08/06/2009 08:42 PM, Jan Lehnardt wrote:
>> On Thu, Aug 6, 2009 at 2:12 PM, Mikeal Rogers<mikeal.rogers@gmail.com>=

>> wrote:
>>> A CLA is required for any contribution, even patches.
>>
>> You mean that we need to go find every person that's ever put a patch
>> on JIRA and get them to sign a legal document?
>=20
> JIRA has a checkbox that is an in-place CLA for patches in JIRA.

Having that checkbox is fantastic. Just to provide some perspective
about how I'm managing CLA agreements for projects I'm managing using
DVCS and people are proposing branches rather than attaching patches:

I have a -contributors team in launchpad, and whenever someone signs the
CLA (as simple as sending an email) I add them to the -contributors
team. I (actually the merge bot) only merge branches from people who
sign the CLA. But, nobody is required to get commit access in order to
create a branch and experiment - commit access to trunk doesn't matter
since it's trivial for anyone to create their own branch to play with
and discuss.

I'm not sure whether there is a team facility in github that could do
the same thing. I hope these ideas are useful for helping find a way to
maintain proper oversight that contributions are properly assigned
without discouraging the use of code collaboration tools.

-elliot


--------------enigA070154F2CE459D18FE26CCB
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkp8GfEACgkQGi43imCMARJK1ACdHfPDB35zX/MyTxBaQyth0Jaa
mYgAnjU6mxHSODjduGGJNUahXqnBnFJn
=Kdxn
-----END PGP SIGNATURE-----

--------------enigA070154F2CE459D18FE26CCB--