Alan Isaac schrieb: > It's your code, so you get to license it. > But if you wish to solicit patches, > a more Pythonic license is IMHO more likely > to prove fruitful.
What license would you suggest? After some reading at [1] and [2] and [3], I found that the Academic Free License (version 2.1) and the Apache License (version 2.0) are considered helpful for contributions to the Python Software Foundation. So far, I haven't used either of these licenses for my own code, and after a little reading the AFL seems okay for me. I would perhaps consider the LGPL [4] as an alternative because it is less restrictive than the GPL. Thoughts or links, anybody? Cheers, Johann [1] http://www.python.org/moin/PythonSoftwareFoundationLicenseFaq [2] http://www.python.org/psf/records/board/minutes/2004-11-09/ [3] http://www.python.org/psf/contrib/ [4] http://www.gnu.org/licenses/lgpl.html -- http://mail.python.org/mailman/listinfo/python-list
