Hi Legal and Tech teams, This is a reminder that the usual time for the biweekly legal call on Thursday will be a joint call with the legal and tech teams to discuss the proposal for changing the

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

Hey, thanks for the references. I’m sorry if I seem to be ignoring existing practices – a lot of the existing workflow and use cases I just don’t have much of a conception of. I very much

Didier, Thank you for submitting your request, which has been added to the SPDX Licenses and Exceptions under consideration workbook: GNU All Permissive License added to the Licenses under

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

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

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

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

I’m sorry if I didn’t make that clearer; I fully intend the things like synonym lists to be separate from the license files. There would likely be an index file of some kind listing out the

Kris, The proposal is interesting, however, one architectural concern would be the comingling of the licenses text and the metadata (location of synonyms, formatting, etc). How would you feel

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

Hi all Providing the license list in multiple formats will help to promote its usage. JSON became very popular during the last few years. I would say it’s the most popular data exchange format

Greetings all, There is a proposal being discussed in a git project issue to create json format files for individual licenses (https://github.com/sindresorhus/spdx-license-list/issues/6). This

New entry for the "Info-Zip License" added to the SPDX Licenses Under Consideration List: https://docs.google.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=695212681

Has SPDX considered the Info-Zip License: http://www.info-zip.org/license.html, with additional explanations here:https://enterprise.dejacode.com/license_library/Demo/info-zip/#license-text? Tom

New entry for the "cURL License" added to the SPDX Licenses Under Consideration List: https://docs.google.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=695212681 I

Hi Julien, From an SPDX License List matching standpoint (see: http://spdx.org/spdx-license-list/matching-guidelines ) the cURL license is indeed a cross between ICU

corrected link for meeting minutes is: http://wiki.spdx.org/view/Legal_Team/Minutes/2015-10-15 (and reinstated minutes for Sept 17) J. SPDX Legal Team co-lead opensource@...

Full name: GNU All Permissive License Short Identifier: GAPL OSI-Approved: no URL:

Here’s a little something to bring a smile to your face on a Friday: http://esr.ibiblio.org/?p=6867 :) Jilayne