Daniel: Thank you for your e-mail. Your comments are helpful. As to the listing of additional exceptions, my initial list had a notation that it was not exhaustive because I just kept finding more and more... and more and more. That is part of what raised this question regarding the license expression syntax. We should certainly add the ones you identified to the list. But I think this list could be a near bottomless pit.
-Tom * * * * * * * * * * * * 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 > -----Original Message----- > From: dmger...@gmail.com [mailto:dmger...@gmail.com] On Behalf Of > dmg > Sent: Monday, June 09, 2014 1:48 AM > To: Tom Vidal > Cc: Dennis Clark; J Lovejoy; SPDX-legal; Michael Herzog > Subject: Re: link to spreadsheet for exceptions list > > Hi Tom, > > some comments: > > what is called the openVPN exception should perhaps be made more > generic. It has been used by several GPL-ed programs to be able to link to > openSSL. I think it is important nonetheless. > > www.climm.org/source/climm-svn/src/io/io_openssl.c > > httperf.googlecode.com/svn/trunk/httperf/src/lib/ssl_writev.c > > https://svn.nmap.org/nmap-exp/aca/nmap/nsock/src/nsock_ssl.c > > this one is of the GPL-2+: > > svn.aircrack-ng.org/trunk/src/osdep/airpcap.c > > there are some exceptions that have basically evolved over time due to > changes in the owner of the company. the two that I can think of are: > > the Digia QT-> to Nokia-QT > and the mysql FOSS -> Oracle FOSS > > maybe there is a way to tie them. I have not looked at them to see how they > are different, but I have seen them. > > > I don't think you have this one (RedHat ELFUtils) > > https://android.googlesource.com/platform/external/elfutils/+/5a6aed9ada > 7eb3148d749cd0721bbfc119ad9fe8/libdwfl/dwfl_addrdie.c > > or this one (Guile) > > www.gnuvola.org/software/guile/_fcompat.c > > this is one without a name really, but interesting because it talks about > inheritance: > > opencores.org/ocsvn/openrisc/openrisc/trunk/rtos/ecos- > 3.0/packages/kernel/current/tests/kexcept1.c > > Bruce's exception: > > > http://ftp.fr.netbsd.org/pub/NetBSD/NetBSD-release-5- > 0/src/dist/ntp/libopts/numeric.c > > the FreeRTOS: > > > FreeRTOS is free software; you can redistribute it and/or modify it under > the terms of the GNU General Public License (version 2) as published by > the > Free Software Foundation AND MODIFIED BY the FreeRTOS exception. > >>>NOTE<<< The modification to the GPL is included to allow you to > distribute a combined work that includes FreeRTOS without being obliged > to > provide the source code for proprietary components outside of the > FreeRTOS > kernel. FreeRTOS is distributed in the hope that it will be useful, but > WITHOUT ANY WARRANTY; without even the implied warranty of > MERCHANTABILITY > or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public > License for > more details. You should have received a copy of the GNU General Public > License and the FreeRTOS license exception along with FreeRTOS; if not it > can be viewed here: http://www.freertos.org/a00114.html and also > obtained > by writing to Richard Barry, contact details for whom are available on the > FreeRTOS WEB site. > > do I keep going? :) > > anyway, I'll be happy to help > > > > --dm > > > > > On Fri, May 16, 2014 at 2: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=0AjgLI2c9YWGYdG9heHY4eH > NzY > > 3JXLWpIMXZmQXBFMlE&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=0AmVnI0dGKE > o1dD > > F0ajVveUtRMGFseVVjWS1zV2tCNFE&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=0AmVnI0dGKEo1dDF0ajVve > UtRM > > GFseVVjWS1zV2tCNFE&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=0AmVnI0dGKEo1dDF0ajVve > UtRM > > GFseVVjWS1zV2tCNFE&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 > > > > > > -- > --dmg > > --- > Daniel M. German > http://turingmachine.org _______________________________________________ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
