Sweet, thanks. I added a link to the participation guidelines page in the wiki. Hopefully one more link will make google pick it up. Peter

Armijn, Now that you have appeared in the NY Times with a Boston Red Sox hat http://www.nytimes.com/2010/09/26/business/26ping.html?src=busln, I feel I must respond quickly. There are a number of

https://fossbazaar.org/pipermail/spdx/ armijn -- --------------------------------------------------------------------------- armijn@... || http://www.gpl-violations.org/

Is the spdx mailing list archived anywhere? I was looking to read up on the past debate around a particular part of the spec and I was unable to locate an archive of the mailing list. It is crucial

I moved it to Home » Wiki » Software Package Data Exchange (SPDX) » Spec Development » Sandbox For Sharing Examples, Ideas, Etc. Not sure if it way my knowledge or permissions or both, but

Hi all, I have posted some examples, along with some notes about them at <http://spdx.org/wiki/openlogic-spdx-10-beta-examples>. The examples are intended to conform to the 1.0 beta version of the

Colleagues, Sorry for sending out the call-in details late. The call will be at the usual Tuesday time the RDF subgroup has been meeting the last 3 weeks. We'll be discussing mechanism for

L. Philip Odence Vice President of Business Development Black Duck Software, inc. 265 Winter Street, Waltham, MA 02451 Phone: 781.810.1819, Mobile:

Kate is doing her best to fix it up asap.

All: this is most likely a known problem, but the draft web page for the spec at http://www.spdx.org/wiki/spdx/specification seems to be quite hard to read (many empty lines), the paragraph numbers

Good point on the copyright holder/copyright information. We could have all of the copyrights combined in one field - e.g. if a file or package has 3 copyrights A, B, and C - we could have a single

Hello All, I am getting up to speed, have taken a close look at the current spec, and have some comments noted below. 3.4 Download URL COMMENT: We may want to have some guideline as to which

Hi, Following up from last week and from SPDX call today, we'll be having a special topic call tomorrow on the licenses. Here's the dial in information for the call tomorrow: US

All: as discussed during today's call here are some pointers to Launchpad RDF: This is an example of a project page: https://launchpad.net/do and the matching RDF

Issue: Not clear how to include SPDX author commentsto the consumers of the SPDX file. For example, a SPDX author may like toinclude a disclaimer, assumptions made, context of the analysis performed

Meeting Time: Sept 23, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC Conf call dial-in: Conference code: 7812589502 Toll-free dial-in number (U.S. and Canada): (877) 435-0230 International dial-in

Colleagues, Those interested in participating in the RDF track, please reconvene next Tuesday. Among other hot topics, we'd like to review in more detail the relationship between SPDX and other

Hello Everyone, The SPDX team is hard at work on completing the spec and nailing down all of the license details. To make sure we are successful in getting SPDX accepted and adopted, we are working

The main problem is that these terms are not really context free. If you see: "This (program|library|software) is (release|made available) under the GPL version 2", you will all probably agree

I agree, distribute and make available have very different legal implications. I also believe that licensed and released are not equivalent to distribute Please consider the environment before