Contributor Agreements for Patches - was [Jython-dev] Jython on Google AppEngine!
A question that arose on this thread, which I'm forwarding for context (and
we're quite happy about it too!):
- What is the scope of a patch that requires a contributor agreement?
This particular patch on #1188 simply adds obvious (in retrospect of course)
handling on SecurityException so that it's treated in a similar fashion to
IOException (possibly a bit more buried), so it seems like a minor patch.
- Do Google employees, working on company time, automatically get treated
as contributors with existing contributor agreements on file with the PSF?
If so, are there are other companies that automatically get this treatment?
- 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).
In these matters, Jython, as a project under the Python Software Foundation,
intends to follow the same policy as CPython.
- Jim
---------- Forwarded message ----------
From: Frank Wierzbicki
I submitted 1188 and I'm a Google employee working on company time. Let me know if anything further is needed, but we have quite a few contributors to the Python project working here. Excellent, and thanks! 1188 was already slated for inclusion in our upcoming RC, but knowing that it is in support of GAE moves it up to a very high priority.
-Frank ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Jython-dev mailing list Jython-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jython-dev -- Jim Baker jbaker@zyasoft.com
participants (3)
-
"Martin v. Löwis"
-
Jim Baker
-
Tobias Ivarsson