Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-06 Thread Steven D'Aprano
On 05/03/13 09:08, Brett Cannon wrote: Depends on your paranoia. If you're worried about accidentally lifting IP merely by reading someone's source code, then you wouldn't want to touch code without the CLA signed. Now I'm not that paranoid, but I'm still not about to commit someone's code now

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-06 Thread Brett Cannon
On Wed, Mar 6, 2013 at 3:06 PM, Steven D'Aprano st...@pearwood.info wrote: On 05/03/13 09:08, Brett Cannon wrote: Depends on your paranoia. If you're worried about accidentally lifting IP merely by reading someone's source code, then you wouldn't want to touch code without the CLA signed.

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-06 Thread Stephen J. Turnbull
Steven D'Aprano writes: Pardon my ignorance, but how does a CLA protect us in the event of an IP violation? By licensing the content to the PSF, the contributor implicitly claims that he has the right to do so (I think the AFL even has an explicit provenance clause). This protects the PSF

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-06 Thread Terry Reedy
On 3/6/2013 3:06 PM, Steven D'Aprano wrote: On 05/03/13 09:08, Brett Cannon wrote: Depends on your paranoia. If you're worried about accidentally lifting IP merely by reading someone's source code, then you wouldn't want to touch code without the CLA signed. Now I'm not that paranoid, but I'm

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-06 Thread Terry Reedy
On 3/4/2013 3:46 PM, Antoine Pitrou wrote: On Mon, 04 Mar 2013 15:46:48 -0500 Terry Reedy tjre...@udel.edu wrote: 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

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-05 Thread Stephen J. Turnbull
Terry Reedy writes: or a proposal for a change that is given within a bug tracker message? I view a proposal for a change as just an idea. Such usually get re-written by whoever creates an actual patch. Precisely how U.S. law would view it, implying no copyright issue. If this really

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-05 Thread Ezio Melotti
Hi, On Mon, Mar 4, 2013 at 10:46 PM, Terry Reedy tjre...@udel.edu wrote: On 3/4/2013 11:36 AM, Brett Cannon wrote: On Mon, Mar 4, 2013 at 11:30 AM, Brian Curtin br...@python.org mailto:br...@python.org wrote: With this in place I would like to propose that all patches submitted to

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-05 Thread Baptiste Carvello
Le 05/03/2013 04:13, Stephen J. Turnbull a écrit : Mark Lawrence writes: People already use the bug tracker as an excuse not to contribute, wouldn't this requirement make the situation worse? A failure to sign the CLA is already a decision not to contribute to the distribution my 2

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-05 Thread Brett Cannon
On Tue, Mar 5, 2013 at 11:48 AM, Baptiste Carvello de...@baptiste-carvello.net wrote: Le 05/03/2013 04:13, Stephen J. Turnbull a écrit : Mark Lawrence writes: People already use the bug tracker as an excuse not to contribute, wouldn't this requirement make the situation worse? A

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-05 Thread R. David Murray
On Tue, 05 Mar 2013 15:22:07 -0500, Brett Cannon br...@python.org wrote: On Tue, Mar 5, 2013 at 11:48 AM, Baptiste Carvello de...@baptiste-carvello.net wrote: Le 05/03/2013 04:13, Stephen J. Turnbull a écrit : Mark Lawrence writes: People already use the bug tracker as an excuse

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-04 Thread Brett Cannon
On Mon, Mar 4, 2013 at 11:30 AM, Brian Curtin br...@python.org wrote: The full announcement is at http://blog.python.org/2013/03/introducing-electronic-contributor.html, but a summary follows. We've now moved to an electronic Contributor License Agreement form at

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-04 Thread Skip Montanaro
On Mon, Mar 4, 2013 at 10:30 AM, Brian Curtin br...@python.org wrote: The full announcement is at http://blog.python.org/2013/03/introducing-electronic-contributor.html, but a summary follows. ... Brian, Do you want old-timers like me who have a wet-signed fax gathering dust in a box at

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-04 Thread Brian Curtin
On Mon, Mar 4, 2013 at 11:02 AM, Skip Montanaro s...@pobox.com wrote: On Mon, Mar 4, 2013 at 10:30 AM, Brian Curtin br...@python.org wrote: The full announcement is at http://blog.python.org/2013/03/introducing-electronic-contributor.html, but a summary follows. ... Brian, Do you want

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-04 Thread Ben Leslie
On Tue, Mar 5, 2013 at 3:30 AM, Brian Curtin br...@python.org wrote: The full announcement is at http://blog.python.org/2013/03/introducing-electronic-contributor.html, but a summary follows. We've now moved to an electronic Contributor License Agreement form at

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-04 Thread Terry Reedy
On 3/4/2013 11:36 AM, Brett Cannon wrote: On Mon, Mar 4, 2013 at 11:30 AM, Brian Curtin br...@python.org mailto:br...@python.org wrote: The full announcement is at http://blog.python.org/2013/03/introducing-electronic-contributor.html, but a summary follows. We've now moved

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-04 Thread Antoine Pitrou
On Mon, 04 Mar 2013 15:46:48 -0500 Terry Reedy tjre...@udel.edu wrote: On 3/4/2013 11:36 AM, Brett Cannon wrote: On Mon, Mar 4, 2013 at 11:30 AM, Brian Curtin br...@python.org mailto:br...@python.org wrote: The full announcement is at

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-04 Thread Mark Lawrence
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 br...@python.org mailto:br...@python.org wrote: The full announcement is at http://blog.python.org/2013/03/introducing-electronic-contributor.html, but a

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-04 Thread Brett Cannon
On Mon, Mar 4, 2013 at 4:33 PM, Mark Lawrence breamore...@yahoo.co.ukwrote: 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 br...@python.org mailto:br...@python.org wrote: The full announcement is at

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-04 Thread Terry Reedy
On 3/4/2013 3:46 PM, Antoine Pitrou wrote: On Mon, 04 Mar 2013 15:46:48 -0500 Terry Reedy tjre...@udel.edu wrote: On 3/4/2013 11:36 AM, Brett Cannon wrote: 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

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-04 Thread Mark Lawrence
On 04/03/2013 22:08, Brett Cannon wrote: On Mon, Mar 4, 2013 at 4:33 PM, Mark Lawrence breamore...@yahoo.co.uk mailto:breamore...@yahoo.co.uk wrote: 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,

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-04 Thread Stephen J. Turnbull
Mark Lawrence writes: People already use the bug tracker as an excuse not to contribute, wouldn't this requirement make the situation worse? A failure to sign the CLA is already a decision not to contribute to the distribution, no matter how noisy they are on the tracker and list. I think

Re: [Python-Dev] Introducing Electronic Contributor Agreements

2013-03-04 Thread Terry Reedy
On 3/4/2013 7:51 PM, Mark Lawrence wrote: Who's talking source code, you're previously mentioned *ALL* patches needing a CLA. Does this mean you have to sign a CLA for a one line documentation patch? It it is a one char typo, I would not bother downloading the patch, or adding a person to