Soeren, welcome, and thanks for the incremental licenses -- Licenses that come up in day-to-day practice are high value for SPDX. Thanks, Tom Tom Incorvia tom.incorvia@... Direct: (512) 340

Hi Dan, Regarding the equivalent terms. I have seen different commercial legal interpretations based on two of the sets of "equivalent" terms below. I believe that these need to be distinct. With rega

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 tom.incorvia@... Direct: (512) 340-1

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 sh

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

Regarding the GPL / LGPL exceptions -- We formerly decided to treat each combination of license + exception as a separate license since the exception can change the terms materially. For instance GPL

Hi DMG, I was off traveling a bit, so if I may have missed some interim conversations -- hopefully I am addressing the same topic that you are. I don't see how the conjunction of 2 licenses will work

Originally sent 2010-Oct-21. For discussion at today’s License Review Meeting, agenda item, “Python Licenses”. Tom Tom Incorvia tom.incorvia@... Direct: (512) 340-1336 Mobile: (408) 499 685

Hi Mark, I agree that there could be many variants. Since we will not be able to interpret the additional terms in any clean fashion (including a certainty that an included term is or is not a “furthe

Please find attached a jpeg that details Python licensing (for today’s Python agenda item in the SPDX Licensing teleconference). Tom Tom Incorvia tom.incorvia@... Direct: (512) 340-1336 Mob

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 particu

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, regardles

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 licens

For Today’s Legal Stream Call (attached). Tom Tom Incorvia tom.incorvia@... Direct: (512) 340-1336 Mobile: (408) 499 6850

Hi Jilayne, Thanks for getting the next rev of the license list out! Regarding the BSD licenses: I did some of the original work on the BSD licenses. Below is the post from June 2010. Fine if we rethi

Hi SPDX Team, Most of the links on the SPDSX site are not working – I was trying to get to the license list. Tom Tom Incorvia tom.incorvia@... Direct: (512) 340-1336 Mobile: (408) 499 6850

Agree. Tom Incorvia tom.incorvia@... Direct: (512) 340-1336 Mobile: (408) 499 6850

Re: new version of License List uploaded Hi Jilayne, On the legal call today I offered to do a last look at the Debian / SPDX license name differences. I agree with Kim: The exclusion of “.0” in cases

Re: new version of License List uploaded - Regarding the MIT license. This is a VERY well-established license, #4 on the Black Duck site, is listed in expected form the OSI site, etc. I have not seen

Perhaps we stick with the version of MIT that is listed at http://www.opensource.org/licenses/mit-license.php as a way to include this license in the standard list -- it is too commonly used to exclud