I wonder if (at least going forward) it makes sense to use an archival URL service like https://perma.cc/ to create a URL that preserves the relevant site at the time the license was added to the

Whoops -- accidentally just sent this to Till, re-sending to the full list: = = = = = Hi Till, please see my thoughts inline below: [SDW] From a quick search on the Internet Archive, that URL appears

Dear all, Sorry to bring this up again. 1. I suggest to correct the information on https://spdx.org/licenses/Unicode-TOU.html The link provided under "Other web pages for this license" points to

Yes, amazing! From:Spdx-legal@... <Spdx-legal@...> on behalf of Kate Stewart <kstewart@...> Date: Friday, February 17, 2023 at 9:06 PM To: Steve Winslow <swinslow@...> Cc: Spdx-legal@...

Wow! 40 new licenses.... that's a milestone for the license list additions, I think. Well done Steve, Jilayne, Richard, Mary, and all other contributors to this release!

Hello all, The version 3.20 release of the license list is now tagged and live at https://spdx.org/licenses. 40 (!) new licenses / exceptions were added to the

Hi all, I have now updated the process documentation at https://github.com/spdx/license-list-XML/blob/main/DOCS/request-new-license.md with links to the videos Steve and I made in December. We will

Hi all, We have our call today, here are a few other agenda items and some issues that need some eyeballs (and then maybe we don't need to discuss) and 1) GSoC

Thank Rohit! That would be awesome! On 2/9/23 1:44 AM, Rohit Lodha wrote:

Hey Jilayne, I would be happy to co-mentor this project on spdx-online-tools. Apart from this idea, we can include many other open issues especially around testing improvements which can be taken up

Hi SPDX-legal, I have added a potential project for GSoC related to improvements to the SPDX License Submission tool, especially as relates to generating the files once a license is

Hi everyone! As every year, Google runs their Summer of Code program, where contributors get the opportunity to become part of Open Source communities. The SPDX Project has participated in the

I was involved implementing SPDX license IDs as package license metadata for a few package managers. How to handle licenses that don't have IDs came up every time. `LicenseRef-*` would get mentioned,

Sorry for the short notice reminder. Given the end of the month and next release time frame is rapidly approaching, we’ll focus today’s meeting on divvying up work to get licenses added. I also

+1 to everything Steve just wrote, with one comment. License namespaces were the first thing that came to my mind when reading the thread. Thanks that you confirmed that the proposal was never really

Thanks all for your comments in this thread. I'm not going to try to reply here to every comment, but wanted to note a few pieces that might be informative to folks who are less deep in the SPDX

If the idea is really to hunt down every license lurking in every potentially popular public package, I can see how distro adoption's a real big deal. Congrats! I worry about more work for distro

Could I make a suggestion rooted in some engineering history here. In the early days we tried to make global lists of relevant features (IANA port numbers, reference constants, etc) and allowed

Maybe start assigning ids for these with a format like vanity-xxx and that might make people think twice about it and actually put some work into really explaining why they need yet-another-license