Re: GPL + exceptions issue
Jilayne Lovejoy <Jlovejoy@...>
So, for purposes of the license list - am I to add a new line item for
toggle quoted messageShow 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
|
|