~ Kate Stewart [2020-05-07 03:37 +0200]: Same goes for GPL-2.0 and the like. That's understandable, and a reasonable workflow. Is there any schedule for the completion of the addition of

Kernel community still recognizes GPL-2.0+ as valid, although we've deprecated it. The header quoted is fine. The conventions are documented in the kernel community trees, and the intention is when

My understanding from being on the linux-spdx mailing list is that this is intentionally tolerated for existing SPDX-License-Identifier notices because it was correct SPDX syntax under the earlier

wrote: No. Look again: GPL-2.0+ is right at the bottom of the list under "Deprecated Licence Identifiers". James

I just got this note from one of my developers. Is he correct? Should we or someone send a patch to Linux project? ..m

Hello spdx-legal list, In light of the upcoming updates to the SPDX website hosting, we are pushing back the release date for the 3.9 license list by two weeks. We are now targeting the release for

hello, I downloaded the 3.8.2 release from python.org and this only seems to be true for one variant of the license text that is used in the PC version of Python:

Hi all, I'm Mary, long time lurker. I searched the wiki, the meeting minutes, and messages, but I couldn't find an answer to my question. Sorry if it is a repeat. My problem is not with the ancient

Thanks, Steve and Kyle. The link to the draft is particularly helpful. I don't want to rehash the many, many discussions about which licenses should be included in the official list; suffice to say,

Hi Richard, Here are some minutes from a previous review mentioning a potential long term solution for non-listed exceptions:

Hi Richard, Thanks for this -- all good points and I agree, in the example you gave I'd represent it in the way you described. As an FYI, regarding custom exceptions (and agreed that the example you

If you have a standard license text (that maps to one of the SPDX license identifiers) coupled with some additional nonstandardized terms, which are not captured by anything in the exceptions

Hello Andrew, Thanks for submitting these three for consideration. If you're available to join today, you're of course welcome, though today's discussion will be focusing on finalizing the items for

Hello all, the next regularly-scheduled SPDX legal team meeting will be today, Thursday, Apr. 23 at 9AM PDT / noon EDT. The primary agenda item will be to discuss license requests currently tagged

Hi All I have submitted the three variants of V2 of the CERN-OHL using the licence submission tool, with the proposed SPDX identifiers: CERN-OHL-2.0-P CERN-OHL-2.0-W CERN-OHL-2.0-S Please let me know

Hi Luis, hope you (and others) are staying safe and healthy as well. Echoing Kyle, "LicenseRef-" is part of the spec syntax and is defined in Appendix IV of the spec. [1] In an actual SPDX document,

Luis, `LicenseRef-*` is technically part of the license expression syntax, too. But it mostly comes up in the context of (private, shared) SPDX XML files. I'm not aware of any package managers that

👋🏼 hope everyone is doing as well as they can under the circumstances. Is there any documentation for, or examples of, correct usage of License Ref? I've been looking this morning and can't

This would be a good time to note that folks who care about their software freedom cannot effectively participate in SPDX, and not only because the conferencing solution is proprietary software

Quoting Jeremiah C. Foster (2020-04-15 18:57:24) For the pragmatic angle of "does it work reliably" I agree that Jitsi is a viable option. Any conferencing service _can_ become unreliable when