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

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

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

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

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

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

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

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