Hi all, did you know: „the and any this you license software for that not use with may code such agreement other terms under are rights work your all from shall source including copyright provided wil

Hi Sebastian, Sorry - I've been negligent at sending out the follow-up meeting information. I missed the end of last week's call, but I believe it was decided to not have a call this week due to the L

Dear all, I thought there was supposed to be a Namespace Proposal meeting at this time today, but I've joined the video call and there are only a couple of others here. Best wishes, Sebastian

Hi all, With a conference going on and end of quarter, we’ll skip our call this week. Please have a look at any open GitHub issues in the meantime! Jilayne Sent from my phone, please excuse brevity an

All, I strongly support Gary's approach of identifying requirements first, then identifying and selecting from technical solutions that meet all requirements. The requirements are: * The SPDX legal te

Greetings SPDX tech and legal teams, A reminder we are continuing the license namespace discussions tomorrow, Friday, 10 June 2022, at the same time (15:00 UTC, 8AM Pacific). We will be using the Lega

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