Hi Team,

I have updated the SPDX License List exceptions spreadsheet at
https://docs.google.com/a/nexb.com/spreadsheet/ccc?key=0AmVnI0dGKEo1dDF0ajVveUtRMGFseVVjWS1zV2tCNFE&usp=sharing#gid=0


with material taken from Tom Vidal's list of GPL exceptions at
https://docs.google.com/spreadsheet/ccc?key=0AjgLI2c9YWGYdG9heHY4eHNzY3JXLWpIMXZmQXBFMlE&usp=sharing

I took the liberty of updating Tom's spreadsheet with some notes to
indicate what actions I took or what concerns I encountered.  Here is an
overall comment that emerges from looking at a bunch of these things:

License "exceptions" that specify lists, frequently long lists, of other
associated and/or eligible licenses are not necessarily all that
well-defined and i'm not sure that they belong on the list of standard SPDX
license exceptions.  In one case (Aptana) the text is reasonably
manageable, but most license exceptions of this sort (where the exception
name often contains "FOSS" or "FLOSS") make me a little nervous about
whether these lists of licenses and/or components might be subject to too
much change over time.  So I'm going to suggest a guideline that we leave
these out.  I left the Aptana  and DigiRule exceptions in the list as
examples for discussion purposes.

Just one of the many little things we need to work out!  Looking forward to
our next Legal Group meeting on Thursday, 05/29/2014.

Regards,
Dennis Clark
nexB inc.



On Thu, May 15, 2014 at 10:38 AM, Tom Vidal <tvi...@agmblaw.com> wrote:

> Dear all: Here is the link to my original list of exceptions:
>
>
>
>
> https://docs.google.com/spreadsheet/ccc?key=0AjgLI2c9YWGYdG9heHY4eHNzY3JXLWpIMXZmQXBFMlE&usp=sharing
>
>
>
> Supposedly, anyone with the link can open this.  If you have trouble, let
> me know.
>
>
>
> * * * * * * * * * * * *
> Thomas H. Vidal, Esq.
> Abrams Garfinkel Margolis Bergson, LLP
> 5900 Wilshire Boulevard, Suite 2250
> Los Angeles, CA 90036
> Direct Dial: 310.300.2950 | Facsimile:310.300.2901
> tvi...@agmblaw.com |www.twitter.com/thomasvidal
> www.linkedin.com/in/thomashvidal
>
>
>
> *From:* spdx-legal-boun...@lists.spdx.org [mailto:
> spdx-legal-boun...@lists.spdx.org] *On Behalf Of *Dennis Clark
> *Sent:* Wednesday, May 14, 2014 11:27 AM
> *To:* J Lovejoy
> *Cc:* SPDX-legal; Michael Herzog
> *Subject:* Re: link to spreadsheet for exceptions list
>
>
>
> Hi SPDX Legal Team,
>
>
>
> Jilayne reminded me that we need to address the license exceptions on the
> Fedora Good List.   I have pulled what I determined to be appropriate
> specimens from that list and updated the SPDX License List exceptions
> document:
>
>
> https://docs.google.com/a/nexb.com/spreadsheet/ccc?key=0AmVnI0dGKEo1dDF0ajVveUtRMGFseVVjWS1zV2tCNFE&usp#gid=0
>
>
>
>
> Happy reading!
>
> Dennis
>
> nexB Inc.
>
>
>
>
>
> On Fri, May 9, 2014 at 4:46 PM, Dennis Clark <dmcl...@nexb.com> wrote:
>
> Hi SPDX Legal Team,
>
>
>
> I have updated the SPDX License List exceptions working document with
> enough examples of Exceptions (I think) to generate a lively discussion in
> our next SPDX legal group meeting.  Hopefully by looking at these examples,
> we can start to gather the criteria for including Exceptions on our
> standard list, as well as begin to define the best way to identify and
> classify each one.
>
>
>
> The document is defined so that anyone with the exact URL can read it.
> Jilayne is the doc owner if you would like to request update permission.
>
>
>
> Here is the link:
> https://docs.google.com/spreadsheet/ccc?key=0AmVnI0dGKEo1dDF0ajVveUtRMGFseVVjWS1zV2tCNFE&usp#gid=0
>
>
>
> Cheers,
>
> Dennis
>
> nexB Inc.
>
>
>
> On Thu, May 1, 2014 at 11:59 AM, J Lovejoy <opensou...@jilayne.com> wrote:
>
> Hi All,
>
>
>
> As per our meeting this morning, I created a new shared spreadsheet for
> creating the list of license exceptions as per the new license expression
> language discussion at Collab Summit.  This will be our working document;
> Dennis has taken the task of owning it and leading the effort for
> populating the list.  I have made the spreadsheet shared with the exact url
> (as opposed to needing to send invites) so that it should be easier for all
> to access during our next meeting.  Here is the link:
> https://docs.google.com/spreadsheet/ccc?key=0AmVnI0dGKEo1dDF0ajVveUtRMGFseVVjWS1zV2tCNFE&usp#gid=0
>
>
>
> (meeting minutes to come soon)
>
>
>
> Cheers,
>
> Jilayne
>
>
>
> SPDX Legal Team co-lead
> opensou...@jilayne.com
>
>
>
>
>
> _______________________________________________
> Spdx-legal mailing list
> Spdx-legal@lists.spdx.org
> https://lists.spdx.org/mailman/listinfo/spdx-legal
>
>
>
>
>
_______________________________________________
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal

Reply via email to