Hello all, The version 3.15 release of the license list is now tagged and live at https://spdx.org/licenses. 4 new licenses were added to the list: COIL-1.0 Community-Spec-1.0 FDK-AAC Linux-man-pages-

Previously I've been generally against the idea of encouraging folks to use the test/simpleTestForGenerator/*.txt files for anything other than the automated tests for the XML files. Mostly for the re

Hi Richard, Thanks for sharing this question. I've been mulling it over and don't have a good answer, so here instead are a few disjointed thoughts. My main hesitation with an "If-Needed-exception" (a

Jilayne, I agree with this. Projects, organizations, license stewards, etc. may all have recommendations about whether or how standard license headers should or shouldn't be used for particular licens

You have been invited to the following event. SPDX Legal Team meeting - 2022 When Every 2 weeks from 12pm to 1pm on Thursday from Thu Jan 6, 2022 to Sat Dec 31, 2022 Eastern Time - New York Calendar s

Hi Sebastian, Thanks for checking on this. I think this is meant to be the schedule -- let me know if the invites aren't lining up correctly: * General Meeting: First Thursday of every month, 11AM-noo

Hi all, This is a follow-up from the discussion last summer at [1], based on the conversation during the Legal Team call this past week. Folks may want to re-read the (long) thread there, which has li

Thanks Alan, Max and Alexios for your thoughts. A couple of responses inline below: Even setting aside the use case that REUSE has raised here (reproducing license texts), there's another good reason

Hi Sebastian (and spdx-legal list), My turn to apologize for the slow reply here :) For the next legal team meeting, we'll stick with today's call at the usual time of noon Eastern, to avoid confusion

Hello all, The version 3.16 release of the license list is now tagged and live at https://spdx.org/licenses. 6 new licenses were added to the list: App-s2p DL-DE-BY-2.0 Elastic-2.0 Jam SchemeReport X1

Hello SPDX-legal list, On last week's Legal Team call, we agreed to switch the timing for team calls going forward, as discussed in this thread. So instead of alternating Thursdays, Legal Team calls w

You have been invited to the following event. SPDX Legal Team - 2nd Thursdays 2022 When Monthly from 12pm to 1pm on the second Thursday from Thu Feb 10 to Sat Dec 31 Eastern Time - New York Calendar s

You have been invited to the following event. SPDX Legal Team - 4th Thursdays 2022 When Monthly from 12pm to 1pm on the fourth Thursday from Thu Feb 24 to Sat Dec 31 Eastern Time - New York Calendar s

Hi Max, circling back on this thread and your question: We briefly discussed this as a follow-up on the last legal team call, and agreed that there did not appear to be any significant objections to m

Thank you Gary, Rohit and the GSoC students! I saw that the test license requests are coming through, so thanks for that in particular :) Steve

Thanks all! One note just for consideration here: the version numbering for the License List has at least a syntactic meaning also within the spec itself, for SPDX documents: see https://spdx.github.i

Hello all, The version 3.17 release of the license list is now tagged and live at https://spdx.org/licenses. 5 new licenses were added to the list: Arphic-1999 Baekmuk Bitstream-Vera KiCad-libraries-e

Hello spdx-legal team (cc spdx-tech team), Some of you may recall the conversations in 2019 and 2020 around the idea of adding a "license namespace" concept to the SPDX spec. This was intended to be a

Hello spdx-legal team (cc spdx-tech team), Similar to my separate email earlier today, I'd also encourage interested folks to take a look at the draft annex in PR #464 at https://github.com/spdx/spdx-

Hi all, Our regularly-scheduled 4th Thursday meeting will be at the usual time this Thursday. There are two topics that I'd like us to discuss, as there has been active discussion on the issue threads