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:

When: Thursday, March 12, 2015 11:00 AM-12:00 PM. (UTC-05:00) Eastern Time (US & Canada)Where: Bridge info enclosed*~*~*~*~*~*~*~*~*~* Reminder, the General Meeting has been moved to this

Apologies, despite have read through carefully 3 times…I meant March 12. From: Phil Odence <podence@...> Date: Wednesday, March 4, 2015 at 3:01 PM To: "spdx@..." <spdx@...>, "spdx-legal@..."

The Feb 5 meeting will be postponed 1 week to Thurs. Feb 12. (outside US, note that US will be on daylight savings time next week so the call will be an hour off of normal for you). The main thrust

Meeting minutes below. Also, here’s information on SPDX participation at CollabSummit. Big thanks to Jack for pulling it all together.

Again, thanks to Bruno Grasset from Valeo for a great presentation. Hope to see everyone at CollabSummit. Time to make your plans. http://events.linuxfoundation.org/events/collaboration-summit

The January meeting with be on Jan 8 at 8am PST, 11am EST, and 16:00 GMT. We’ll start with Bruno Grasset from Valeo describing their use of SPDX. Please make every effort to join. His slides are

When: Thursday, January 08, 2015 11:00 AM-12:00 PM. (UTC-05:00) Eastern Time (US & Canada)Where: Bridge info enclosed*~*~*~*~*~*~*~*~*~* Rescheduling the January meeting as it would normally fall on

Hello all, If you have any interesting SPDX story to tell, even a short one, we would love to have you share it at the Collab Summit. The event is Feb 18-20 in Santa Rosa, California.