Hi Legal, Tech teams, I just want to clarify my understanding of capitalization sensitivity for SPDX license ids and license expression operators: Appendix IV states: License expression operators (AND

Hi Jilayne, You can refresh your memory on the discussions (2015-2020) by reading https://github.com/spdx/spdx-spec/issues/63 😉 I still like my example from that thread: Do we really want to be able t

Hi all, We are going to aim for the end of next week for the 3.14 release - giving everyone an extra week to tidy up any outstanding issues. So, if you haven't gotten to something, you have a bit more

Hi all, In the scope of REUSE we've noticed [^1] that just providing LPGL-3.0* – as downloaded from SPDX – in a repo does not suffice as it requires its mother license, GPL-3.0*. LGPL could be seen as

Hi SPDX-legal, I've been chatting to some of the Fedora folks about adopting the use of SPDX license identifiers in its package spec files. I just posted a comment/ proposal to a PR that was opened so

Hi Anthony, Thanks for pointing this out. I tried to add a comment, but it appears to be closed. Thomas is active in the SPDX-tech team, but would be nice if someone from the SPDX-legal could add a bi

Hello all, The version 3.14 release of the license list is now tagged and live at https://spdx.org/licenses. 13 new licenses were added to the list: CC-BY-NC-SA-2.0-FR CC-BY-NC-SA-2.0-UK CC-BY-2.5-AU

Hi all, Just a reminder we have our legal call tomorrow/Thursday at the usual time and place. https://meet.jit.si/SPDXLegalMeeting Paul and I both have a conflicts, but Steve will there. Now that we h

Hi all, I wanted to raise a question I've been thinking of in light for Fedora and other open source OS distros looking to adopt use of SPDX license identifiers in various ways. One concern that has b

Hi OSI, Just noting that this does not appear to be on the SPDX License List currently. Copying SPDX-legal here as well. A new license request has been added here: https://github.com/spdx/license-list

Hi all, Just a reminder of our regularly scheduled call in a bit over an hour. The docfest is going on today as well, so we may have thinner attendance, but we’ll meet and work on looking at issues an

Hi all, We have our regular call today at noon EDT. We'll catch up on any other "intros"; I think Warner was going to give an update on the SPDX work in FreeBSD (if you are ready to do so), and get or

Hi all, We have our regularly scheduled call today in a bit over an hour from now. We’ll get back to reviewing issues and prepping for the next release - as well as any updates on other on-going proje

Hi Pierre, I am moving the general SPDX list to BCC and sending this via the SPDX legal list, as that is the right place for this question! Also not - I have approved your message and copied you here

Hi all, I came across a "variant" of the Caldera license. Here is what we have on SPDX: https://spdx.org/licenses/Caldera.html But this project - http://heirloom.sourceforge.net/sh.html has this licen

And thereby missing all of you lovely people. We’ve a big deadline this week so I need to use that hour for other things, unfortunately. --V -- VM (Vicky) Brasseur Director, Senior Strategy Advisor Op

Dear all, My pull request regarding the BSD-1-Clause license is up and ready to be merged (https://github.com/spdx/license-list-XML/pull/1350). :) I've also been looking through the LicenseListPublish

Hey all, Since SPDX's effort to include all remaining approved Fedora licenses in SPDX has stalled out (again!)[1][2], can someone *please* add the FDK-AAC identifier to SPDX? It's blocking my submiss

Hi all, We have our regularly scheduled call tomorrow, Thursday at 10 am mountain standard time. (the US has now pushed our clocks forward, so we should be back to our normal time zone gap differences