Provide a proposed Full Name for the license or exception. -------------------------------------------------------------------------------- The Open Game License v1.0 Provide a proposed Short

Hi All, We have a legal call tomorrow and will resume discussions on whether improvement to the license templates are warranted. I have moved the various feedback sent via email to this page:

Hi SPDX Legal Team, I’ve recently run across the Open Cascade project: http://www.opencascade.com/content/open-source-development http://dev.opencascade.org/ For versions <= 6.6.0, they

Hi All, On account of version 2.2 of the SPDX License List being live and LinuxCon Europe being a few days away, we’ll skip this week’s call and resume on Oct 15th with a recap of LinuxCon and

The meeting minutes from today’s call are posted here: http://wiki.spdx.org/view/Legal_Team/Minutes/2015-09-17 Thanks, Jilayne SPDX Legal Team co-lead opensource@...

Hi Nuno, Gary, Philippe, and Sam, This is really great information. We did not have time to discuss on the call today, as the focus was on items for the v2.2 release of the license list, but I’d

Hi Sam, Thanks for sharing your own feedback on license templatization / regexes. Here's mine. a) have you used the existing markup for matching purposes? No.

Didn't use the markup. At the time haven't found documented the pattern keywords to find inside each license term. For example, one can find [xxxx]-[xxxx], [Owner Organization], <AUTHOR>. However,

Hi Sam, Responses inline below: Gary

Yes and No: ScanCode uses an SPDX-inspired/derived markup, but instead of reusing the markup directly from the main license texts, markup is transformed in a simpler {{mustache-like}} syntax added

3) License matching templates/markup: We have a task to add markup to some of the standard headers and have also had input to add/edit markup on existing licenses. As a result of the latter, it has

Hi All, In preparation for Thursday’s call, please review the following items in advance for our agenda. Announcements and updates (#1) are here only for your information (nothing to discuss on

Hi All, Sorry for the last minute notice, but I have some pressing things to deal with. We’ll resume as usual on Sept 17th at the usual time and number. Thanks, Jilayne SPDX Legal Team

Point for point.. Retaining the original text explicitly is not mutually exclusive with maintaining it in a single file, however it is not the approach I favor anyway (for reasons of content

Hi Kris, Both good points. Responses inline below.

Two things: 1) The easiest and least complex way to retain the original text is to retain the original text explicitly. 2) The existence of a single tool written in a single language is much less

Jilayne: The subsequent comments are fine indeed. I still think that markup for detection and reference texts would be best handled separately in the long run, yet the volume is still rather low and

HI All, Just going through some old threads. Philippe - do the subsequent comments clear up your concerns? If not, can you explain further? It’d be great to get some follow-up

We had a small turnout today due to LinuxCon, but we had a good discussion and have queued up some things for next call: http://wiki.spdx.org/view/Legal_Team/Minutes/2015-08-20 Jilayne SPDX Legal Team

Hi All, We have the SPDX Legal call in about half an hour. Agenda: 1) update from LinuxCon Seattle (assuming people who were/are still there joint the call!) 2) standard headers that need markup -