Re: SPDX Agenda/Minutes

Kim Weins

I also agree that we should decouple spec from licenses. We need a way to
add licenses without having to rev the spec. Otherwise we will get lots of
spec revisions or very few license updates.

I know there has been some concern that if the list of licenses is not
"fixed" with the spec version, you won't know what list of licenses you need
to be able to "understand" when you get an SPDX file based on a particular
version of the spec. I'd like to dig into this use case more, since it seems
to me that any tooling or even manual review processes can be designed to
just pull the latest and greatest version of licenses from the website.

The only issue is that you may get an SPDX file that has something marked as
an "Other" license that is now in the standard license repo. That
shouldn't really be a problem, since all the "Other" licenses will have full
license text in the SPDX file.

Here's an example:

Company A creates SPDX on 1/1/2011 using latest set of standard licenses at
that point. They identify:
File A has Standard License A
File B has Standard License B
File C has Other License C
File D has Other License D

On 2/1/2011, License C is added to standard license repo

Company B reviews SPDX on 3/1/2011
All of the info is still valid -- since License C and D are in the SPDX
file. Company B could choose to update the SPDX file as:
File A has Standard License A
File B has Standard License B
File C now has STANDARD License C
File D has Other License D

Am I missing something here?


On Wed 9/8/10 12:48 PM, "dmg" <dmg@...> wrote:

From the minutes:

Our implicit path had tied a fixed license list of licenses to the
spec rev, but JohnE put forth an impassioned argument as to why they
should be decouples...

I throw my support behind JohnE proposal. It addresses many of the
issues I have discussed before.


(hopefully I can make wake up in time for the meeting, but it is tough
to only have 5 hrs of sleep :)

On Wed, Sep 8, 2010 at 11:24 AM, Philip Odence
<podence@...> wrote:
Per discussion late meeting, agendas will be going out in bodies of emails
and minutes will go out as links to archive at
I'll strive to get minutes out a week in advance, though I'm behind this
time. Here's where they are posted (note that Kate is still editing, so they
won't be final until tonight)
Meeting Time: Sept 9, 8am PDT / 10 am CDT / 11am EDT / 16:00 GMT

Conf call dial-in:
Conference code:  7812589502
Toll-free dial-in number (U.S. and Canada):  (877) 435-0230
International dial-in number: (253) 336-6732
For those dialing in from other regions, a list of toll free numbers can be
Note, we will be using a different URL for each meeting for purposes of
taking attendance. When you login please include your full name and company
name, so I can just copy/pate into minutes. THX.

Administrative Agenda

Approval of minutes
Outreach and evangelism:

Common Messaging/Presentation ­ PhilO

Industry Venues ­ PhilR

Website ­ PhilO/Martin

Roll Out Plans - KimW/JohnE

Action Items
Note: Drafting related action items are embedded in
the Wiki.

€ PhilO/Martin - Update on participation page where to join (suggestion was
to put link in text, not just at top, consider "I want to use the spec, vs.
I want to contribute to the spec" in navigation section.
€ Kate- Transfer document (.pdf) back to WIKI.
€ PhilO- Update standard presentation with LinuxCon2010 input
€ Kate- Clean up the sharing analysis to what is accurate.
€ Kate- Publish the current version number of the specification in brackets
behind reference
€ Kim/PhilO- Add and element of 'What's in this for me?" to presentation
€ JeffL (w/Bill/Gary- Update zlib based on new specification
€ All- Look for new examples to add to site.
€ PhilK- Explore possibility of LF hosting source for SPDX tools.
€ Gary- Explore other possible hosting options
€ PhilO- Start making minutes available via link.
€ BillS- Start up RDF sub-group. Solicite members.

Technical Agenda

SPEC - current status and open areas - Kate
RDF focus group - current status - Bill
Tools - update from Gary, and others.

L. Philip Odence
Vice President of Business Development
Black Duck Software, inc.
265 Winter Street, Waltham, MA 02451
Phone: 781.810.1819, Mobile: 781.258.9502
podence@... (my blog)

Spdx mailing list

Kim Weins | Senior Vice President, Marketing
Follow me on Twitter @KimAtOpenLogic

650 279 0410 | cell
Follow OpenLogic on Twitter @OpenLogic

OpenLogic, Inc.
Headquarters, Broomfield, Colorado

Join { to automatically receive all group messages.