Hi all, We have a meeting at noon eastern time today. Let’s have a look at: - Steve’s PR as per his previous email, see https://github.com/spdx/license-list-XML/pull/1883 codifying the exceptions

Hello spdx-legal folks, Sending this to the mailing list as a heads-up since it relates to the License Inclusion Principles [1]. Following from recent SPDX legal team calls, we realized that the

Sorry for the "Reply" instead of "Reply all". The answer to Patrice-Emmanuel's question may interest other members. Please find it below: ---------- Forwarded message --------- De : Sihem Ben Sassi

Interesting tool! Question: Which of your license features covers that according to the license, "distribution" includes providing remote access or SaaS? Ever visited the joinup tool ? --

Just a reminder that the regularly scheduled SPDX Legal team meeting is beginning momentarily, on our usual Jitsi link: https://meet.jit.si/SPDXLegalMeeting Best, Steve

Dear Henrick, Sorry for the late answer. I was very disappointed as people are interested in the web tool and the document I shared, but they haven't collaborated (in return) by taking the survey. I

Hey Sebastian, Thanks for pointing this out, I have pushed a fix and we have the latest licenses also at scancode-licensedb.aboutcode.org now. Ayan

Hi everyone, We have updated the SPDX license list version in scancode-toolkit to the newly released version 3.20, and this is also updated and available at scancode-licensedb.aboutcode.org. This will

Hello Steve, Am 22.02.23 um 20:54 schrieb Steve Winslow: Sounds good to me! Thanks for taking care. Ok. Makes sense to me. Agreed. What about

Hi all, We have our usual call at the top of the hour. Now that the big 3.20 release is out, we'll reset on some process-related stuff, look at some of the issues that didn't

Hi Till, Regarding the Unicode Terms of Use: since there is a new and substantively different set of terms at https://www.unicode.org/copyright.html, I agree it would be appropriate to add them to the

Hi Steve, Thanks for looking into this issue. I have a few additional remarks below: Am 21.02.23 um 20:55 schrieb Steve Winslow: Well, there are several cases in which

Just one additional bit of information on this topic. The JSON format for the License data was upgraded a couple years back to reflect the state of the “other URL”. The implementation

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