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

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

We could just have a separate license for GPL+amendment for all the common exceptions. This fits the current license model pretty well. However, it means that an uncommon set of amendments would

Hi, Okay,I uploaded the v1.2 spreadsheet and accompanying guidelines in a word doc asattachments to a new Wiki page here: http://www.spdx.org/wiki/license-list-v12 Disregardmy previous email

See comments in ALL CAPS below. I will send an email when the latest License List and Guidelines document has been uploaded to the Wiki so everyone can just look at it there. Jilayne

I agree these licenses are a bit redundantseeming and not well differentiated. However, I think when a license hasbeen approved by the OSI, we need to just stick with the license name they use.

Hello, Jilayne Lovejoy said on Thu, Nov 04, 2010 at 09:19:54AM -0600: I think there is a problem line 32 of the LicenseList v1.2 file: Column A mentions version 1.0 wheresas column B says 3.0. I

Hereis the next version of the license list (v1.2) that includes the license textand some other changes discussed via email. I also updated the “guidelines”document and listed any changes in this

Sorry this is a little late, although I shared some of this data on previous calls. The SPDX presentation at OWF went well. We had about 40 people or so, and most of them stayed an hour over the

Big power outage in the Black Duck neighborhood so I may not be able to start up the web session. I'll be on my cell phone for the audio part. Please try to log in but don't be surprised if it doesn't

Meeting Time: Nov4, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC. NOTE THAT EUROPE HAS TURNED CLOCKS BACK TO STD TIME, BUT THE US HAS NOT YET, SO THE TIME DIFF FROM US TO EUROPE IS 1 HR LESS THAN

Today's call dial-in details: SPDX RDF Sub-group Mtg 8 (TODAY) Tuesday October 26, 11AM eastern time Toll-free dial-in number (U.S. and Canada): (877) 435-0230 International dial-in number: (253)

I created a page in the wiki to list spec change proposals, <http://www.spdx.org/wiki/proposals>. New proposal should be added to this list when they are created. Once we get an issue tracker up and

The proposals for surfacing information regarding the origin a files are * <http://www.spdx.org/wiki/proposal-2010-10-21-2-file-origin> : Two new properties of File that store the name and URL of

As requested, I've uploaded Kim's slides from Open World Forum: http://spdx.org/system/files/kim_weins-spdx.pdf -- Martin Michlmayr Open Source Program Office, Hewlett-Packard

9:00 AM - 10:00 AM November 12, 2010 Location: Dial in below We will review the license list and address issues. US 866-740-1260 Int'l http://www.readytalk.com/support/international-numbers.php ID

FYI, I did a compare of Python 3.2 LICENSE to the muchearlier 2.0.1 AFTER removing the history information – so the comparestarted with the statement “TERMS AND CONDITIONS FOR ACCESSING

Details for the call will be: Toll-free dial-in number (U.S. and Canada): (877) 435-0230 International dial-in number: (253) 336-6732 Conference code: 7812589502 For those dialing in from other

Last week's meeting was out of the normal every 2 weeks rhythm, and we are now back on normal schedule. The call is Oct 21 at 8am PDT/11AM EDT/15:00 UTC. Once again, I apologize in advance for

To the best of my understanding, there have been several different Python license versions, but the licenses are self-superseding, in that as new versions arrive, they automatically apply. ~tom