License List spreadsheet v1.1
Hello All,
Attached is a first run at the license list info in a spreadsheet format as Kate mentioned below. I also included a word document with some explanations, "guidelines" I made up as I went along, and issues or questions I noticed. There are also some specific comments within the spreadsheet cells.
I didn't add too many more licenses, although I think we will need to add some. I wanted to take some time to identify other licenses not on the list that I have come across most often during audits, as perhaps others in the group can do as well.
Cheers,
Jilayne Lovejoy
From:
spdx-bounces@... [mailto:spdx-bounces@...] On Behalf Of Tom Incorvia
Sent: Tuesday, October 19, 2010
8:41 AM
To: kate.stewart@...;
spdx@...
Subject: RE: spec is back in WIKI
format again,,,
Hi Kate, I will be glad to give the license information spreadsheet a good review when it is available (or review an interim document). Tom
Tom Incorvia
Direct: (512) 340-1336
Mobile: (408) 499 6850
From:
spdx-bounces@... [mailto:spdx-bounces@...] On Behalf Of kate.stewart@...
Sent: Tuesday, October 19, 2010
9:32 AM
To: spdx@...
Subject: spec is back in WIKI
format again,,,
|
|
Click here to report this email as spam.
This message has been scanned for viruses by MailController.
Hi Jilayne,
Thanks for working on this. I have been traveling, so hopefully I am not too far behind the conversations.
Here are a few very minor things:
- I agree that we should use “Apache” as the short name
- There is a comma in license full name “ISC License (Bind, DHCP Server)”
- Regarding the entry GNU Library or "Lesser" General Public License v2 or v2.1 only”, I agree that this entry should be removed, and we should have a 2.0 or later; and a separate 2.1 or later as you recommend.
- On the Nethack GPL, the 3.4.3 specification actually refers to the program rather than the license – there is no suffix for the Nethack license.
- The Python license may have versions – I am not certain -- they take the time to restate the license with each release – however, I comparisons of some of the “official licenses” and they were the same. Anyway, we will need to dig into Python a bit in terms of versioning and relationship to CNRI – I don’t have the bandwidth for this right now, but hopefully there is someone on the team who is deep into Python licensing
Tom
Mobile: (408) 499 6850
Sent: Tuesday, October 19, 2010 11:23 AM
To: Tom Incorvia; kate.stewart@...; spdx@...
Subject: License List spreadsheet v1.1
Hello All,
Attached is a first run at the license list info in a spreadsheet format as Kate mentioned below. I also included a word document with some explanations, "guidelines" I made up as I went along, and issues or questions I noticed. There are also some specific comments within the spreadsheet cells.
I didn't add too many more licenses, although I think we will need to add some. I wanted to take some time to identify other licenses not on the list that I have come across most often during audits, as perhaps others in the group can do as well.
Cheers,
Jilayne Lovejoy
From:
spdx-bounces@... [mailto:spdx-bounces@...] On Behalf
Of Tom Incorvia
Sent: Tuesday, October 19, 2010 8:41 AM
To: kate.stewart@...; spdx@...
Subject: RE: spec is back in WIKI format again,,,
Hi Kate, I will be glad to give the license information spreadsheet a good review when it is available (or review an interim document). Tom
Tom Incorvia
Direct: (512) 340-1336
Mobile: (408) 499 6850
From:
spdx-bounces@... [mailto:spdx-bounces@...] On Behalf
Of kate.stewart@...
Sent: Tuesday, October 19, 2010 9:32 AM
To: spdx@...
Subject: spec is back in WIKI format again,,,
|
|
Click here to report this email as spam.
This message has been scanned for viruses by MailController.
- The Python license may have versions – I am not certain --To the best of my understanding, there have been several different
they take the time to restate the license with each release – however, I
comparisons of some of the “official licenses” and they were the same.
Anyway, we will need to dig into Python a bit in terms of versioning and
relationship to CNRI – I don’t have the bandwidth for this right now,
but hopefully there is someone on the team who is deep into Python licensing
Python license versions, but the licenses are self-superseding, in that
as new versions arrive, they automatically apply.
~tom
FYI, I did a compare of Python 3.2 LICENSE to the much earlier 2.0.1 AFTER removing the history information – so the compare started with the statement “TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING PYTHON”.
The licenses are the same other than adding to the list of copyright years and changing the title “CWI PERMISSIONS STATEMENT AND DISCLAIMER” TO “CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2”. I have attached the compare.
I also noticed that the license link for particular versions of the Python software don’t always match. For instance the link http://www.python.org/download/releases/2.4.6/license/ links to a license titled 2.4.4 license. Similarly the URL for 3.0.1 points to a license titled 2.6.1. There are others.
Between versions 2.4.4 and 2.5 “Version 2” is added to the license. But the changes continue to be limited to extensions of the copyright years.
I believe that the discrete licenses are:
- CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2
- CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1
- Python Version 1 (Covers Python after 1.6.1 and prior to 2.5)
- Python Version 2 (Covers Python 2.5 and after)
Tom W, what do you think – some of the specificity in versions and release is removed as the licenses get newer. I have not looked for language re self-superseding.
Thanks,
Tom
Tom Incorvia
Direct: (512) 340-1336
Mobile: (408) 499 6850
From: Tom "spot" Callaway [mailto:tcallawa@...]
Sent: Wednesday, October 20, 2010 2:03 PM
To: Tom Incorvia
Cc: Jilayne Lovejoy; kate.stewart@...; spdx@...
Subject: Re: License List spreadsheet v1.1
On 10/20/2010 02:56 PM, Tom Incorvia wrote:
> - The Python license may have versions – I am not certain --
> they take the time to restate the license with each release – however, I
> comparisons of some of the “official licenses” and they were the same.
> Anyway, we will need to dig into Python a bit in terms of versioning and
> relationship to CNRI – I don’t have the bandwidth for this right now,
> but hopefully there is someone on the team who is deep into Python licensing
To the best of my understanding, there have been several different
Python license versions, but the licenses are self-superseding, in that
as new versions arrive, they automatically apply.
~tom
This message has been scanned for viruses by MailController - www.MailController.altohiway.com
Originally sent 2010-Oct-21. For discussion at today’s License Review Meeting, agenda item, “Python Licenses”. Tom
Mobile: (408) 499 6850
Sent: Thursday, October 21, 2010 9:51 AM
To: Tom "spot" Callaway
Cc: Jilayne Lovejoy; spdx@...; kate.stewart@...
Subject: RE: License List spreadsheet v1.1
FYI, I did a compare of Python 3.2 LICENSE to the much earlier 2.0.1 AFTER removing the history information – so the compare started with the statement “TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING PYTHON”.
The licenses are the same other than adding to the list of copyright years and changing the title “CWI PERMISSIONS STATEMENT AND DISCLAIMER” TO “CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2”. I have attached the compare.
I also noticed that the license link for particular versions of the Python software don’t always match. For instance the link http://www.python.org/download/releases/2.4.6/license/ links to a license titled 2.4.4 license. Similarly the URL for 3.0.1 points to a license titled 2.6.1. There are others.
Between versions 2.4.4 and 2.5 “Version 2” is added to the license. But the changes continue to be limited to extensions of the copyright years.
I believe that the discrete licenses are:
- CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2
- CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1
- Python Version 1 (Covers Python after 1.6.1 and prior to 2.5)
- Python Version 2 (Covers Python 2.5 and after)
Thanks,
Tom
Tom Incorvia
Direct: (512) 340-1336
Mobile: (408) 499 6850