The Linux Foundation has a Bugzilla instance that we should be able to use. * Peter Williams <peter.williams@...> [2010-09-07 16:25]: -- Martin Michlmayr Open Source Program Office,

Now that the technical sub-group has initiated its work i think it would be worth having a issue tracking system. This would allow us to reliably track issues with the spec and to make sure nothing

Hello, I may be able to attend the last half-hour of the talk, if my previous conf call with my partner doesn't extend to much :-(. Bruno. kate.stewart@... said on Thu, Sep 02, 2010 at

hi! It was not entirely trivial to get it working: the documentation and the actual names of files and patches are not in sync, so it cost me about 10 minutes to get everything working (I will send

Hi Bill, I can attend, and want to be considered part of the working group. Thanks, Kate

hi everybody, Is anybody being successful at building and using ninka? So far I have not heard from anybody (neither good or bad news). Based on feedback we are planning to make a wider

Anyone is welcome; Gary, Jeff, Peter have accepted. Details below. SDPX RDF Sub-group Mtg 1 Tuesday Sept 7, 11AM eastern time Toll-free dial-in number (U.S. and Canada): (877) 435-0230 International

Tuesday 11AM eastern (8AM pacific) works for me. Gary

This will work for me. Jeff

SPDX colleagues: As per the last con-call, here's a shout out to those who wish to collaborate outside of the current bi-weekly calls to focus on the details of the RDF representation of an SPDX

Bonjour Patrick, CeCILL licenses have been mentioned before by others as well, so unless someone objects I'll just add them to the next draft with some of the others that have been discussed and

Provided that we still go with the license text repository, what about something like a "diff"-standard for exceptions and variations of the standard licenses? (i.e. a standardized syntax describing

an/listinfo/spdx What is the intended use case for an spdx file? So far it appears to me that it is supposed to describe one single software package. If so, I indeed see us attaching giant data

RUFFIN> The problem is that except for licenses like GPL or Apache2 a RUFFIN> lot of licenses MIT, BSD, Apache1.1 contain a part which is RUFFIN> different from one license to another (such as the

This is fantastic, thanks Martin! I'll bring the content from Fedora over to the spdx.org site this week. Apologies for missing last Thursday's meeting (Thursdays are... busy for me). Was there any

* Tom spot Callaway <tcallawa@...> [2010-08-24 21:26]: Sure, I'd agree with that. The Drupal wiki functionality has been enough for our needs so far but MediaWiki (or another proper wiki)

The problem is that except for licenses like GPL or Apache2 a lot of licenses MIT, BSD, Apache1.1 contain a part which is different from one license to another (such as the copyright and for old BSD

Peter> Once a license is "approved" and placed in the repo it should be Peter> immutable. That way there is no chance of the text changing once the Peter> license name is in use. Perhaps this is a

Hi Jilayne, Welcome. :) Text for each exception, should include exception and original licenses. Web site is behind on being updated. What is most accurate right now is the spec document at

Hello, I'm new to the mailing list so forgive me if any of my questions/observations are redundant or minimally informed. I had a couple thoughts regarding various posts and the license