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) 336-

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 NORMAL

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

Update from OWF 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 hou

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

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

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

They are now up on the website. http://www.spdx.org/wiki/20101104-minutes L. Philip Odence Vice President of Business Development Black Duck Software, inc. 265 Winter Street, Waltham, MA 02451 Phone:

So, for purposes of the license list - am I to add a new line item for each GPL + exception? If so, does anyone want to help me generate a list of the various commonly used exceptions with some attent

I would agree with Peter's assessment below. To be clear, my interpretation of this would be that this would remove the various "or later" instances from the actual license list and then that option w

Reminder -- for people that want to attend ------ Original Appointment From: kim.weins@... When: 9:00 AM - 10:00 AM November 12, 2010 Subject: License Review Meeting Location: Dial in below We will re

Hi guys, for some reason mywhen I sent the reminder from my calendar, it didn't show time zone. The meeting is 11ET, 9MT, 8PT, etc Kim Kim Weins | Senior Vice President, Marketing kim.weins@... Follow

Agenda for License Review Meeting GPL “or later” issue - is there consensus on list around leaving as is in terms of listing “GPL v2 only” separately from “GPL v2 or later” with differentiation showin

Hello All, Attached is a first run at the license list info in a spreadsheet format as Kate mentioned below. I also included a word document with some explanations, "guidelines" I made up as I went al

I think that we need to take into account the fact that GPLv3 permits six "additional terms" (see below). Since they you could have many variants, perhaps the best approach is to have a category for "

- >> Which is only true at that moment of time. If/when GPLv4 is available, >> you would miss that one. So it's important to keep the fact that the >> author stated that it's GPLv2+ to cover this. >>

The two open, overlapping, proposals for showing the provenance of files in an SPDX document are up for approval at the next SPDX full group meeting. Proposal 2010-10-21-2 [1] proposes adding optional

Examples posted Finally! Sorry about the delay. I took the examples that were already in the wiki area (http://spdx.org/wiki/openlogic-spdx-10-beta-examples) that Peter W posted some time ago and post

Meeting Time: Nov18, 8am PDT / 10 am CDT / 11am EDT / 16:00 UTC. http://www.timeanddate.com/worldclock/converter.html Conf call dial-in: Conference code: 7812589502 Toll-free dial-in number (U.S. and

Hi everybody, We are releasing a minor update to our license identification tool. The major difference with version 1.0-pre1 is packaging. We no longer require the user to download and patch the sente