There are two versions of the Contributor Agreement
http://www.python.org/psf/contrib/contrib-form-python/ and http://www.python.org/psf/contrib/contrib-form/
It looks like the first one is old, because http://www.python.org/psf/contrib/ points to the second one.
Victor
On 3/23/2011 9:31 PM, Victor Stinner wrote:
http://www.python.org/psf/contrib/contrib-form-python/ and http://www.python.org/psf/contrib/contrib-form/
It looks like the first one is old, because http://www.python.org/psf/contrib/ points to the second one.
I believe you are right. The only difference is the addition of the line 'The currently acceptible licenses..." and a vaguely remember some discussion just before I signed it (the 2nd version with the addition).
We should ask the pydotorg list to fix this. Should we at the same time requet the assition of a field for the committer's user name?
regards Steve
On Mar 23, 2011, at 10:41 PM, Terry Reedy wrote:
On 3/23/2011 9:31 PM, Victor Stinner wrote:
http://www.python.org/psf/contrib/contrib-form-python/ and http://www.python.org/psf/contrib/contrib-form/
It looks like the first one is old, because http://www.python.org/psf/contrib/ points to the second one.
I believe you are right. The only difference is the addition of the line 'The currently acceptible licenses..." and a vaguely remember some discussion just before I signed it (the 2nd version with the addition).
python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Terry Reedy wrote:
On 3/23/2011 9:31 PM, Victor Stinner wrote:
http://www.python.org/psf/contrib/contrib-form-python/ and http://www.python.org/psf/contrib/contrib-form/
It looks like the first one is old, because http://www.python.org/psf/contrib/ points to the second one.
I believe you are right. The only difference is the addition of the line 'The currently acceptible licenses..." and a vaguely remember some discussion just before I signed it (the 2nd version with the addition).
The first one is old and was mainly used when we started to ask for CLAs. It optionally also covers past contributions.
The second one is the one we currently use. It does not have the clause to cover past contributions, since we now expect contributors to sign the CLA before the contributions go into the repository.
Could someone please arrange for the first URL to redirect to the second one ?
Thanks,
Marc-Andre Lemburg eGenix.com
Professional Python Services directly from the Source (#1, Mar 24 2011)
Python/Zope Consulting and Support ... http://www.egenix.com/ mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
::: Try our new mxODBC.Connect Python Database Interface for free ! ::::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/
On Thu, 24 Mar 2011 09:40:44 +0100, "M.-A. Lemburg" <mal@egenix.com> wrote:
The second one is the one we currently use. It does not have the clause to cover past contributions, since we now expect contributors to sign the CLA before the contributions go into the repository.
Note that this rarely happens in practice. At least, it rarely happens that the PSF has the form in hand and acknowledged prior to the first significant checkin.
-- R. David Murray http://www.bitdance.com
R. David Murray wrote:
On Thu, 24 Mar 2011 09:40:44 +0100, "M.-A. Lemburg" <mal@egenix.com> wrote:
The second one is the one we currently use. It does not have the clause to cover past contributions, since we now expect contributors to sign the CLA before the contributions go into the repository.
Note that this rarely happens in practice. At least, it rarely happens that the PSF has the form in hand and acknowledged prior to the first significant checkin.
True and there's work underway to fix this.
I should have phrased the reply more carefully: while in the ideal case, we should have the CLA before adding significant contributions to the repo, it is fine if we only get it in time for a release containing the contribution.
Also, given that we have for many years worked without any CLA, let's not overrate all this. If a contributor uploads a patch to the tracker, he or she will know that the patch could end up in the repo and subsequent release - regardless of whether they sign a CLA or not.
Legally this is a gray area, though, which is why the PSF introduced the CLA some years ago.
Note that the PSF may also get into trouble if such code was submitted by someone who doesn't own the copyright to the patch. This has happened a couple of times in the past (fortunately, before cutting the release), so for larger contributions, it's better to double check with the patch provider and get the CLA before adding the code to the repo. The problem is then no longer a PSF problem, but one of the patch provider.
-- Marc-Andre Lemburg eGenix.com
Professional Python Services directly from the Source (#1, Mar 24 2011)
Python/Zope Consulting and Support ... http://www.egenix.com/ mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
::: Try our new mxODBC.Connect Python Database Interface for free ! ::::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/
participants (5)
-
M.-A. Lemburg
-
R. David Murray
-
Steve Holden
-
Terry Reedy
-
Victor Stinner