classification
Title: Use BSD0 license for code in docs
Type: enhancement Stage:
Components: Documentation Versions:
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: docs@python Nosy List: bbayles, docs@python, terry.reedy, toddrjen
Priority: normal Keywords:

Created on 2020-03-07 03:50 by toddrjen, last changed 2020-06-26 20:59 by bbayles.

Pull Requests
URL Status Linked Edit
PR 17635 open toddrjen, 2020-03-07 03:50
Messages (4)
msg363573 - (view) Author: Todd Jennings (toddrjen) * Date: 2020-03-07 03:50
Currently using code examples and recipes from the documentation is complicated by the fact that they are all under the Python 2.0 license.  Putting them under a more permissive license, particular the BSD0 license, would make them much easier to use in other projects.
msg364139 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2020-03-14 03:25
What is the complication?  The Python license is already rather permissive.  Anyway, there is a name@mail.python.org address for trademark issues, listed on the site, and it might be appropriate for license legal questions also.  Or this might be a question for discuss.python.org.
msg364276 - (view) Author: Todd Jennings (toddrjen) * Date: 2020-03-16 02:34
Hi Terry,

Please take a look at the linked PR.  This was already discussed on the python-ideas mailing list and Guido agreed this is a good idea.  It is currently waiting on a PSF board decision.  Guido requested I create a blurb, and that required a corresponding issue number, so I created this issue.  

But to answer your question, the problem is incorporating code into an existing project.  The whole point of examples and recipes is that they be used in other projects.  But keeping them under the Python 2.0 license makes this hard, since it requires all the documentation keep that same license.  So you can't use, say, an itertools recipe without keeping a separate license for that code, and some way to identify which code falls under that license.
msg364286 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2020-03-16 05:12
OK.  I looked at the PR.  Normally, issue comes first, with justification and approval status.
History
Date User Action Args
2020-06-26 20:59:51bbaylessetnosy: + bbayles
2020-03-16 05:12:27terry.reedysetmessages: + msg364286
2020-03-16 02:34:57toddrjensetmessages: + msg364276
2020-03-14 03:25:33terry.reedysetnosy: + terry.reedy
messages: + msg364139
2020-03-07 03:50:57toddrjencreate