Jilayne, this is awesome news -- thanks for passing it along! Looking forward to us working with the Fedora community to support them adding SPDX license IDs across the distro. Steve

If I'm following the discussion correctly, I'd agree with Warner here. If I take code that I received under BSD-2-Clause and I redistribute it under MIT, I'm really redistributing it under MIT subject

Greetings SPDX tech and legal teams, A reminder we are continuing the license namespace policy discussions on this Friday, July 1, 2022, at the same time as the prior meetings (15:00 UTC, 11AM Eastern

Hi Gary, thanks for all of the above. Just one comment for folks on the list of agenda items -- for items 2 and 3, I think this may have accidentally copied over the same problem statement as item 1:

Hi Sebastian, thanks for this — this is an interesting proposal! I want to give it some more thought, but here are a couple initial reactions: For MATCHES-LICENSE, I gather the idea is that this is in

If there is time left during the meeting on Thursday, we may also discuss the following issue (and I'd encourage folks to take a look and weigh in there as well): 3. Adding NONE to the License Express

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

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-

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

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

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

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

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

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

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

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

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

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