[Python-Dev] Contributor Agreements for Patches (original) (raw)
[Python-Dev] Contributor Agreements for Patches - was [Jython-dev] Jython on Google AppEngine!
"Martin v. Löwis" martin at v.loewis.de
Wed Apr 8 20:37:39 CEST 2009
- Previous message: [Python-Dev] Contributor Agreements for Patches - was [Jython-dev] Jython on Google AppEngine!
- Next message: [Python-Dev] Contributor Agreements for Patches - was [Jython-dev] Jython on Google AppEngine!
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
* What is the scope of a patch that requires a contributor agreement?
Unfortunately, that question was never fully answered (or I forgot what the answer was).
* Do Google employees, working on company time, automatically get treated as contributors with existing contributor agreements on file with the PSF?
Yes, they do.
If so, are there are other companies that automatically get this treatment?
Not that I know of.
* Should we change the workflow for roundup to make this assignment of license clearer (see Tobias's idea in the thread about a click-though agreement).
I think we do need something written; a lawyer may be able to tell precisely.
I still hope that we can record, in the tracker, which contributors have signed an agreement.
In these matters, Jython, as a project under the Python Software Foundation, intends to follow the same policy as CPython.
Please keep pushing. From this message alone, I find two questions to the lawyer, and one (possibly two) feature requests for the bug tracker.
Regards, Martin
- Previous message: [Python-Dev] Contributor Agreements for Patches - was [Jython-dev] Jython on Google AppEngine!
- Next message: [Python-Dev] Contributor Agreements for Patches - was [Jython-dev] Jython on Google AppEngine!
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]