Date
1 - 3 of 3
GPL + exceptions issue
|
Jilayne Lovejoy <Jlovejoy@...>
So, for purposes of the license list - am I to add a new line item for
toggle quoted message
Show quoted text
each GPL + exception? If so, does anyone want to help me generate a list of the various commonly used exceptions with some attention to how they are named? The exceptions tend to be associated with a specific project, but the text of the exception has to do with what is being excepted from the GPL copyleft license requirement. For the purposes of matching the correct exception to what's found in an actual file - both pieces of information (name and substance of exception) can be useful... Does anyone have any thought on how to handle this in terms of the actual list? -----Original Message-----
From: spdx-bounces@... [mailto:spdx-bounces@...] On Behalf Of Peter Williams Sent: Friday, November 05, 2010 9:25 AM To: spdx@... Subject: Re: License List v1.2 wiki page created On 11/5/10 5:08 AM, Tom Incorvia wrote: We formerly decided to treat each combination of license + exceptionas a separate license since the exception can change the terms materially. For instance GPL + Classpath is more permissive than LGPL. From a practical point of view, the exception creates a different license. Tom Thanks for pointing that out. That agreement must have been reached before i joined the group. I agree that approach makes the most sense. We could make the relationship explicit by defining a dc:hasPart property on the license+exception with the value of the original license. This would allow tools to more easily show how various license are related to one another. Peter Williams www.openlogic.com _______________________________________________ Spdx mailing list Spdx@... https://fossbazaar.org/mailman/listinfo/spdx |
|
|
|
dmg
The list will grow n^2 to the number of GPL licenses. Why not consider
toggle quoted message
Show quoted text
the exception as a conjunction of two licenses for the purpose of the spec? One the GPL, and the other the exception. This will also help to simplify new exceptions as they appear. --dmg On Tue, Nov 9, 2010 at 10:13 AM, Jilayne Lovejoy <Jlovejoy@...> wrote:
So, for purposes of the license list - am I to add a new line item for |
|
|
|
Tom Incorvia
Hi DMG,
toggle quoted message
Show quoted text
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 with our model -- we track "a license". I thought that we had previously agreed that the licenses would be distinct (resulting in, say, "GPL 2.0 with Classpath Exception" as a single license). I am in the commercial world, and we need to treat the License + exception as a distinct "agreement". Thanks, Tom Tom Incorvia tom.incorvia@... Direct: (512) 340-1336 Mobile: (408) 499 6850 -----Original Message-----
From: spdx-bounces@... [mailto:spdx-bounces@...] On Behalf Of dmg Sent: Tuesday, November 09, 2010 12:25 PM To: Jilayne Lovejoy Cc: spdx@... Subject: Re: GPL + exceptions issue The list will grow n^2 to the number of GPL licenses. Why not consider the exception as a conjunction of two licenses for the purpose of the spec? One the GPL, and the other the exception. This will also help to simplify new exceptions as they appear. --dmg On Tue, Nov 9, 2010 at 10:13 AM, Jilayne Lovejoy <Jlovejoy@...> wrote: So, for purposes of the license list - am I to add a new line item for -- --dmg --- Daniel M. German http://turingmachine.org _______________________________________________ Spdx mailing list Spdx@... https://fossbazaar.org/mailman/listinfo/spdx This message has been scanned for viruses by MailController - www.MailController.altohiway.com |
|
|