Regarding the Python licensing,

Kim is correct.  http://python.org/psf/summary/ clearly states that the PSF Python releases are licensed under the stack of licenses.  So my statement regarding a particular PSF version being licensed under one and only one license is incorrect for the PSF-related licenses – it is the stack.   

If we can get a statement from the PSF saying that the stack license applies regardless of version (even the old CWI versions), then we will only need the stack-license (although it has a “pick whatever applies to your release” nature that is a bit different than what we have been doing).  This is a bit different than the Mozilla tri-license where the end user picks . . .

The alternative to listing the stack-license would be to have PSF say on a version by version basis when a stack / stack-subset / individual license applies.  Messy – that is the route that I was taking.    

Tom

Tom Incorvia

tom.incorvia@...

Direct:  (512) 340-1336

Mobile: (408) 499 6850

New Proposal for SPDX license tracking related to the Python project and Python “License”:

1.       Track "Python License" separate from "Python License Stack". 

a.       The Python Programming Language, regardless of version, would be attributed to the stack

b.      However, other projects can be licensed specifically under the Python License (which is ONLY the first license in the stack).

That’s it.

An update to the graphic from two weeks ago is attached.  The highlighted portions are new.

Tom

Some additional information has been added to the Python license graphic (attached). 

Based on the new information, it appears that the stand alone CNRI license on opensource.org is ONLY for the licensing of the beta version of python 1.6.1.  Kate Stewart and I will confirm this with Python Legal. 

Tom

Mobile: (408) 499 6850

For Today’s Legal Stream Call (attached).  Tom