Hi all, Gary asked us to log issues for any improvements we might think of for the SPDX online tools - particularly related to the submit license and generate XML tools. I have just added some notes o

I just posted meeting minutes for today’s call (still need to add those from last meeting). https://wiki.spdx.org/view/Legal_Team/Minutes/2019-03-21 Please note: for merging the final PRs, let’s try t

Hi all, Meant to send this out last night, but as a last minute reminder, we have a meeting today at the top of the hour. Dial-in info: Web conference: http://uberconference.com/SPDXTeam Optional dial

Hi Philippe, I’m not going to re-hash what was a very lengthy and (surprisingly to me) heated discussion on the Linux kernel enforcement statement, since that is all in the email list archives. But as

Hi all, Towards the end of 2018, Richard Fontana submitted the GPL Cooperation Commitment for review to be added to the SPDX License List. We had some discussion about how that might work, but due to

and here is the link to that announcement that I forgot to include before: https://www.finos.org/blog/announcing-the-open-source-license-compliance-handbook ;) Jilayne

Hi SPDX folks (legal and general list), I want to tell you about a project I’ve been working on with Aaron Williamson and the Fintech Open Source Foundation (FINOS) that I think many of you may be int

Hi all, As discussed on a previous call, I’ve added a new doc describing the workflow for adding a new license. This aims to capture the steps for our team members who are shepherding a request throug

Hi Philippe, I’m a bit lost on what the goal of this is. Can you provide a bit more context. I looked at a couple entries and noticed, for example, this one: https://github.com/nexB/spdx-license-names

Hi Kyle, Could I please ask you to submit this via our (somewhat) new and improved system as described here: https://github.com/spdx/license-list-XML/blob/master/CONTRIBUTING.md :) Thanks, Jilayne

Hi All, Just a reminder that we have our bi-weekly call this Thursday at 17:00 GMT (9:00AM PT, 10:00 MT, 11:00 CT, 12:00PM ET). As we are getting close to the “deadline” for getting stuff in for the 3

Sorry for last minute warning! Sent from my phone, please excuse brevity and typographical errors.

in an hour - we’ll pick up where we left off from last call! https://wiki.spdx.org/view/Legal_Team Also: please note - the Open Source Leadership Summit is coming up in Half Moon Bay, March 12-14 - ht

that looks great! Jilayne

Thanks for the update, Elmar. So, the “old” versions that you’ve created along the way for the OSI approval process are not being used in the wild, is that right? It seems like the versioning is more

Hi Kai, I think you are onto the right path in terms of adding the first license and updating our existing Libpng. As to the latter, that would have to be done via matching markup such that the existi

Hi Mark, Philippe, I just had a closer look at this using Alan’s handy License Diff tool, which gave it a close match to MIT-CMU - the only difference between this license and MIT-CMU is: - “and its a

Hi Elmar, It appears that you are still in the OSI review/approval process and as a result the license has evolved a bit. We are tracking it for submission to SPDX here - https://github.com/spdx/licen

https://wiki.spdx.org/view/Legal_Team/Minutes/2019-01-10 Thanks for everyone for a good call and kick off for 2019. Please note action items at bottom and call for everyone to help with new license su

to note, Donald at FSF has already fixed the identifiers - you can see the blog post online here: https://www.fsf.org/blogs/licensing/fsf-licensing-compliance-lab-2018-and-the-future :)