(cross-posting to tech and legal team, as I suspect others may be interested) Hi SPDX-tech team, I just wanted to confirm my understanding of the various formats we now have for the SPDX specification

I'm working on some draft documentation for Fedora around use of SPDX expressions in RPM spec file License: fields. I was surprised to apparently not see anything in the SPDX spec that says that the A

Hi all, We have our regularly schedule call tomorrow/Thursday at noon US eastern time. After a bit of a hiatus, we’ll get back to our usual order of business. Please have a look through the current is

Hi McCoy! I’m moving the SPDX-general list to BCC and replying to SPDX-legal as that is the right place for this discussion. Where is this question coming up in terms of context? That is, are you thin

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

Greetings all, Below is information on the follow-up meetings regarding license namespaces. Please mark your calendars if you are interested in attending – I will not be sending out any calendar invit

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