Just a reminder, we will be continuing the License Namespace discussion this Friday (likely today by the time you get this email) at 15:00 UTC/8AM Pacific at the coordinates below: https://meet.jit.si

Here is an example license list: https://scancode-licensedb.aboutcode.org/ Regards, Dennis Clark

Greetings SPDX Tech and Legal teams, Good discussion today, we were able to close on the problem statements and make progress on the next steps and namespace policies. Minutes from today’s joint call

Hi all, We have our 2nd Thursday of the month meeting today in about 45' (at noon US eastern time). I think we ought to get back to some day-to-day items in terms of new issues and then perhaps a reca

Dear all, On our joint SPDX Legal/Tech meeting today, one of the use-cases that was discussed was No.6: "issue of capturing variants of licenses which match the same listed license per the matching gu

Greetings SPDX tech and legal team members, Thanks to all the attendees of today’s joint tech / legal call where we discussed the namespace proposals. I just created a pull request with the minutes at

Greetings SPDX Tech and Legal Teams, The follow-up meeting to discuss license related issues and requests for the SPDX Specification version 2.3 will be this Friday at 15:00 UTC (8AM Pacific time). We

Hi SPDX legal and tech teams, I was trying to get my head around any and all issues/PRs/topics that are license related. Please let me know if I've missed anything on the list below! Given the pending

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-

(responding via email so I can add spdx-legal mailing list; not sure what mess this will make in Github, so apologies in advance) that is my understanding too There are obvious pros and cons to both a

Dear all, Unfortunately, I will not be able to make tomorrow's SPDX Legal Team meeting. In fact, I will not have an internet connection for the rest of the week, but I'll be back online next week! If

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

Hi, We have our regularly scheduled call today at noon Eastern US time. Tech Team Lead, Gary O'Neall, will be joining us to talk about the SPDX Online Tools! https://tools.spdx.org/app/ Jilayne

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

Hi all, As I was adding milestones to the Github repo for the next couple releases, I wondered... do we just keep going with 3.18, 3.19, 3.20... (and 3.20 looks a lot like 3.2, but I guess that was al

Hi all, I noticed that NPM is using an Artistic-2.0 with additional terms and conditions: ----------------- npm License Copyright (c) npm, Inc. and Contributors All rights reserved. npm is released un

Hi all, We have our regularly scheduled legal team meeting today in about an hour - at noon Eastern Daylight Savings time. We’ll focus on clearing out any tasks, issues, PRs for the 3.17 release! Jila

Just FYI – We will be doing a significant upgrade to the SPDX online tools this morning. The SPDX online tools will be offline this morning for a few minutes to a few hours depending on how the upgrad

Hi Roland, I’m forwarding this to the SPDX-legal mailing list as that is the best place for this question. You also need to join that to post. I don’t have the link to that handy but if you go to the