This event has been changed. more details » SPDX Legal Workstream Call 11ET/10CT/8PT All: This calendar appointment is for the next SPDX Legal Workstream call; where those in Boston for Project

This event has been changed. more details » SPDX Legal Workstream Call 11ET/10CT/8PT All: This calendar appointment is for the next SPDX Legal Workstream call; where those in Boston for Project

The idea of using a human readable format as the primary format in the beta program was mentioned on the cross functional call this morning. It think that is a great idea. However, there did not seem

* Martin Michlmayr <tbm@...> [2011-02-11 10:01]: spdx: 95 spdx-biz: 15 spdx-legal: 21 spdx-tech: 20 -- Martin Michlmayr Open Source Program Office, Hewlett-Packard

This event has been canceled and removed from your calendar. SPDX Legal Workstream Bi-Weekly Call 11ET/10CT/8PT Happy New Year to all. This calendar appointment is for our regular bi-weekly SPDX

I am out of the country and will likely not be able to attend, so Kate will run. Meeting Time: Feb 24, 8am PST / 10 am CST / 11am EST / 16:00 UTC.

Agenda/Minutes 2011 Feb 17 1. Beta program update 2. Volunteers for beta coordinator 3. Beta materials 4. Product management question on tools reqts Participants Kim Weins Phil Koltun Phil Odence

At the recent SPDX general call, I offered to clarify Python licensing and to suggest standard names. This set of licenses is messy, and a long discussion is below. There is not a single logical

You should consider signing up for one or more of the team mailing lists. Going forward we will be limiting the traffic on the SPDX list to summaries of the General Meetings and other high level

One of my ongoing action items is: | MartinM- Report back on # of people on respective mailing lists. DONE, BUT LET'S KEEP UPDATING Here's an update: spdx: 95 spdx-biz: 11 spxd-legal: 17 spdx-tech:

http://www.spdx.org/wiki/2011210-general-meeting-minutes 2011/2/10 General Meeting Minutes Administrative Attendance - 13 Minutes from 27 Jan meeting approved Technical Team Report Gary/Peter created

Meeting Time: Feb 10, 8am PST / 10 am CST / 11am EST / 16:00 UTC. http://www.timeanddate.com/worldclock/converter.html Conf call dial-in: Conference code: 7812589502 Toll-free dial-in number

"LicenseInfoInFile" removes the ambiguity, so going with that seems reasonable. Kate

Bear in mind that "LicenseInformation" is the Tag which is a short form of the full name, "License Information in File." This longer name was roundly supported by folks on the last Legal Team call,

I don't love "LicenseSeen" but i agree that "LicenseInformation" a bit too ambiguous. We should either stick to one format or not specific the format of these ids at all. I lean toward just saying

I think Package should have an optional concluded licensing field also. Given that the value of this property is potentially a disjunctive set of licenses (or license sets) would "Licensing" be

Hi Rockett, Thanks for pulling this all together, and summarizing. :) Sorry I couldn't be on the last call. In reading through the summary couple of thoughts occurred. Can I suggest

SPDX Legal Workstream Members: Below please find the revised Section 5.3 text discussed during our last meeting, for your comment. I will post the same to Bugzilla later today. Many

Whoops, I've got to learn to read ahead.

Daniel, That work is in process; the Legal Team is working on it. You may want to get on their distribution list. The rough plan is to add a field to the spec which is the license for the data in the