Hi Yev, The spec you linked to was the one I created for las week's call. Is there a different document we should be refering to? Thanks, Kate

Here is the spec for the proposed EternalPackage element. While I touch on usage in the beginning, I'll discuss some specific use cases in the context of SpdxTools on the

Hi, We're now less than on month away from LinuxCon, and we wanted to get some information out for those who want to participate in the SPDX 2.0 Bakeoff. If you can make it to Seattle that’s

http://wiki.spdx.org/view/General_Meeting/Minutes/2015-07-02 Thanks again to Gary and the UNO team for the interesting presentation. L. Philip Odence General Manager Audit Services Vice President of

Hi everyone, Thanks for the chance to discuss the UNO SPDX tools at the General Meeting. Here are the links to the GH repositories for projects that are currently active: DoSOCS:

Hi, I would love to hear about SPDX 2 integrated into yocto or Open Embedded if someone has done that. Regards, Jeremiah On Jul 1, 2015 2:09 PM, "Philip Odence" <podence@...> wrote:

I’m trying to spice up every General Meeting with a speaker talking about a special topic, usually their organizations’ use of SPDX or work related to. If you have any ideas for future

Hi Rob, Thanks for you email. To request a new license be added to the SPDX License List, you need to provide the info listed on this page (most of which you already have)

I'm told I should contact you about registering Toybox's "zero clause bsd" license for an official 0BSD acronym/abbreviation. The license text itself (paragraphs 2 and 3 here):

Hi Terin, On the surface the following appears to be syntactically convenient: license-expression = 1*1(simple-expression / compound-expression / "NONE" / "NOASSERTION") but semantically

Hi Terin Neither could we. :-) Ah yes, that should be considered. Right now when NONE or NOASSERTION are permitted, they are associated with the actual fields in the specification (ie.

Kate: I'm unsure of any use case where you would want to mix NONE or NOASSERTION with either simple-expression or compound-expression in the same package. You may however want to use these strings

Hi Terin, Can you give us a real life use case where either "NONE" or "NOASSERTION" should be used in combination with other licenses? If there's a compelling use case as to why it should be

The ABNF in Appendix IV of the 2.0 version of the specification allows for short form identifiers, LicenseRef values or combinations to form a license-expression. However the values "NONE" and

This should be a good one! In addition to the standard agenda, Gary O’Neall start us off speaking about some interesting SPDX happenings in the Javascript and Ruby communities: GENERAL

First, SPDX 2.0 has been released and is available on the website. A press release should be doing out very soon, if not today. As soon as that happens Jack will post a blog with a link to the

This should be a brief one. My aim has been to line up special topics or guest speakers for General Meetings, but I’ve not lined up one for this month. Please let me know if you would be willing to

http://wiki.spdx.org/view/General_Meeting/Minutes/2015-04-02 General Meeting/Minutes/2015-04-02 < General Meeting | Minutes Attendance: 10 Lead by Jilayne Contents [hide] 1 Biz Team Report -

First, I am happy to announce that Gary O’Neall is joining the SPDX Core Team. Gary has been heavily involved in leading SPDX from the outset. Although his focus has been on tools, he has made great

Hi, Just a quick reminder we'll be having a Q&A session about the SPDX 2.0 Specification tomorrow in the monthly general meeting at 11AM EDT/10 AM CDT/8AM PDT. Details of the meeting are: When: