Introduction
As discussed on the last legal call, here's my proposal for enhancing the
markup.
There are two problems that need solving:
1) Maintaining a version of the licenses with just enough markup to aid in
the computer-hard decisions
2) Make computer matching entirely
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 have their own custom license, the Open Cascade
Technology Public License:
Provide a proposed Full Name for the license or exception.
The Open Game License v1.0
Provide a proposed Short Identifier.
OGL-1.0
I neglected to mention that the changes I am suggesting are obviously
version-breaking changes. They would likely be rolled out in SPDX 3.0 (or
later?!) if we’re using semver, and there wouldn’t necessarily be a direct
migration path given that the entire structure around matching licenses
Rob,
Thank you for submitting your request, which has been added to the SPDX
Licenses and Exceptions under consideration workbook:
Open Game License v1.0a
added to the Licenses under consideration worksheet:
Eric,
Thank you for submitting your requests, which have been added to the SPDX
Licenses and Exceptions under consideration workbook:
OCCT Public License
added to the Licenses under consideration worksheet:
Hi Kris,
Thanks for writing up such thorough proposal. This will make it much easier
to discuss some of the specifics.
A couple quick items - you mentioned that you could not find the syntax for
the current text. It is in the SPDX specification PDF file
Hi Kris,
Excellent point on Excel - it really is difficult to do diff's (inside or
outside of Git).
One more detail on the current workflow - we only maintain the license
metadata in the spreadsheet (license ID, header, related URL's), the actual
license text for the templates are in
