Jilayne: I would have loved to join but my travel plans are already set and I am leaving Friday. A bit more of an advance notice would have been needed. Phone would be nice.

If you care about open source compliance automation and if you are going to FOSDEM there is a one day hackathon and meeting taking place the day before FOSDEM on Friday January 31st as "fringe" event,

Hi Aurelien: <aurelien.carlier@...> wrote: As far as I can remember, since this is the same as the BSD-3-Clause license text (using the matching guidelines), it was never added as its own

All: I started working with the Python community to draft what we call a PEP (Python Enhancement Proposal) to adopt SPDX license expressions to document the license of Python packages. You can join th

Hi Thomas! <thomas.steenbergen@...> wrote: FWIW, I agree this is rather common in the wild. It has been tracked and detected as "apple-runtime-library-exception" in the scancode-toolkit since Apr

Dear legal eagles: I just saw that the request to have a proper SPDX license id for the Kernel enforcement statement has been closed [1]. I guess I should have followed the discussion that happened la

Kyle: Thankyou: that's all valuable things to consider indeed and hard earned from the leftpad issues. Though I doubt mere licenses will ever be as successful as npm!

Richard: Let me recap my understanding: I think everyone agrees that we want want more licenses in SPDX. Anyone against this, please voice your concerns now. The review of new licenses for list is an

Richard, Jeff: Agreed. What I am trying to achieve here is to make these become "standard" and known at SPDX. I think this is possible. <Jeff.McAffer@...> wrote: This ideal works in theory b

Hi Jilayne: I sent it quickly during the legal team call on Thursday and sorry for not providing much background then. Here it is: There has been a recent discussion initiated by Mark Atwood to create

See https://github.com/nexB/spdx-license-namespaces-registry/ and https://github.com/nexB/spdx-license-namespaces-registry/pull/1

Hi Mark: We surely could use a way to have namespaces of sorts for extra, non SPDX-listed license identifiers. This is something that I could use alright for ScanCode where we track roughly an extra 1

Hi Marc: We use https://gitter.im/spdx-org/Lobby (which is also accessible by IRC) on the tech side. Should be easy enough to have a legal channel there -- Cordially Philippe Ombredanne

Hi Mark: <atwoodm=amazon.com@...> wrote: It looks to me as a proper historical permission (HPND https://spdx.org/licenses/HPND.html ) This has been detected by the ScanCode toolkit as an HP

If this can help, we have tracked in ScanCode all the 15 known text variations to date: https://github.com/nexB/scancode-toolkit/search?p=1&q=%22this+Commitment+to+be+irrevocable%22&unscoped_q=%22this

This section of the reference text is often enough customized by projects (including Apache's own projects) leading to quite a few too many variants of full license text in the wild so I am all for it

Mike: If I recall correctly: when we started we did add wholesale all the CC licenses without much discrimination. That's an incongruity that I can live with alright.

<kstewart@...> wrote: I listed this because SPDX has issued ids that contained a + in the past. But that's minor alright! I do not care much for the underscore. Good catch!

Alexios: good catch, though even printable may be too generous. A colon is printable and not a supported in a Windows file name for instance. Jilayne: We could/should more simply list the allowed char

Hi Kai: [...] This makes a lot of sense to me. We have been tracking these (see three variants below) in ScanCode and DejaCode for quite a while: - https://github.com/nexB/scancode-toolkit/blob/develo