On Mon, Apr 13, 2009 at 4:44 PM, "Martin v. Löwis" <martin at v.loewis.de>wrote: > > * What is the scope of a patch that requires a contributor > > agreement? > > Van's advise is as follows: > > There is no definite ruling on what constitutes "work" that is > copyright-protected; estimates vary between 10 and 50 lines. > Establishing a rule based on line limits is not supported by > law. Formally, to be on the safe side, paperwork would be needed > for any contribution (no matter how small); this is tedious and > probably unnecessary, as the risk of somebody suing is small. > Also, in that case, there would be a strong case for an implied > license. > > So his recommendation is to put the words > > "By submitting a patch or bug report, you agree to license it under the > Apache Software License, v. 2.0, and further agree that it may be > relicensed as necessary for inclusion in Python or other downstream > projects." > > into the tracker; this should be sufficient for most cases. For > committers, we should continue to require contributor forms. Sounds great to me. Cheers, Tobias -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20090413/02e1f035/attachment.htm>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4