Dear J. Lovejoy, Yes that should work since newer versions can always be auto-applied. Concerning version 1.3 it was not used in practice though I have forgotten to mark it as Draft until the OSI

that looks great! Jilayne

Greeting legal and tech team, Following up on last week’s legal call, Alan Tse and I discussed using some of the license diff features as part of the license submittal process. This resulted in

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

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

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

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://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

Hi Marc: We use https://gitter.im/spdx-org/Lobby (which is also accessible by IRC) on the tech side. Should be easy enough to have a legal channel there -- Cordially Philippe Ombredanne

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 :)

Hi all, I hope everyone had some nice time off and enjoyed the holidays. You should have all gotten a recurring invite from Steve Winslow for the 2019 bi-weekly legal calls at 9am Pacific time. Our

more details » SPDX Legal Team call When Every 2 weeks from 12pm to 1pm on Thursday from Thu Jan 10 to Thu Dec 26 Eastern Time - New York Where https://www.uberconference.com/SPDXTeam

Very heartening! From: "spdx-legal@..." <Spdx-legal@...> on behalf of Jilayne Lovejoy <opensource@...> Date: Monday, January 7, 2019 at 5:02 PM To: "spdx-legal@..." <spdx-legal@...> Subject: Re:

That's great to see! --- Mike Dolan VP of Strategic Programs The Linux Foundation Office: +1.330.460.3250 Cell: +1.440.552.5322 Skype: michaelkdolan mdolan@... ---

and yes, I am aware that they listed the SPDX short identifiers incorrectly and have reached out to the FSF asking for a correction. Still good mention in spirit, though! Jilayne

In case some of you are not on the FSF mailing list, SPDX had a nice mention here! :) Jilayne Begin forwarded message: From: "Donald Robertson, III, FSF" <info@...> Subject: FSF Licensing and

Hi, Latest release of libpng, 1.6.36, updated its license: http://www.libpng.org/pub/png/src/libpng-LICENSE.txt . To cite the homepage at http://www.libpng.org/pub/png/libpng.html : "libpng 1.6.36

Hi all, version 3.4 of the SPDX License List is now live! https://spdx.org/licenses/ You can read release notes here: https://github.com/spdx/license-list-XML I’m really pleased that we got this

Hi Mark: <atwoodm=amazon.com@...> wrote: It looks to me as a proper historical permission (HPND https://spdx.org/licenses/HPND.html ) This has been detected by the ScanCode toolkit as an