[Python-Dev] Introducing Electronic Contributor Agreements
breamoreboy at yahoo.co.uk
Mon Mar 4 22:33:55 CET 2013
On 04/03/2013 20:46, Terry Reedy wrote:
> On 3/4/2013 11:36 AM, Brett Cannon wrote:
>> On Mon, Mar 4, 2013 at 11:30 AM, Brian Curtin <brian at python.org
>> <mailto:brian at python.org>> wrote:
>> The full announcement is at
>> but a summary follows.
>> We've now moved to an electronic Contributor License Agreement
>> form at
>> http://www.python.org/psf/contrib/contrib-form/ which will hopefully
>> ease the signing and sending of forms for our potential contributors.
>> The form shows the required fields whether you're signing as an
>> individual or a representative of an organization, and removes the
>> need to print, scan, fax, etc.
>> When a new contributor fills in the form, they are emailed a copy of
>> the form and asked to confirm the email address that they used (and
>> received that copy at). Upon confirming, the signed form is sent to
>> the PSF Administrator and filed away.
>> The signature can either be generated from your typed name, or you
>> draw or upload your actual written signature if you choose.
>> With this in place I would like to propose that all patches submitted to
>> bugs.python.org <http://bugs.python.org> must come from someone who has
>> signed the CLA before we consider committing it (if you want to be truly
>> paranoid we could say that we won't even look at the code w/o a CLA).
> Either policy could be facilitated by tracker changes. In order to see
> the file upload box, one must login and the tracker knows who has a CLA
> on file (as indicated by a * suffix on the name). If a file is uploaded
> by someone without, a box could popup with the link to the e-form and a
> message that a CLA is required.
People already use the bug tracker as an excuse not to contribute,
wouldn't this requirement make the situation worse?
More information about the Python-Dev