Hi all, We have our regular meeting Thursday at noon Eastern time. The US set back the clocks this past weekend, so we should be back to the usual time intervals. As we move into the next release cycl

Hi all, I deviated slightly from the plan as discussed at our last call regarding updating the FAQs. I went ahead and made a PR here: https://github.com/spdx/license-list-XML/pull/1692 as working in t

Dear all, I'm wondering why https://spdx.org/licenses/Unicode-TOU.html is (still) part of the license list. Could it be deprecated? 1. First of all, the current text of the "Unicode® Copyright and Ter

G'day SPDX gurus, I'm working on a little license matching project [1] leveraging the (great!) SPDX text templates [2], but have noticed that some canonical license texts (e.g. CC-BY-4.0 [3]) don't ma

Dear all, Today, I saw this plop into my inbox and thought that it would also be of interest to many of the SPDX Legal Team members. The Open Source Way is both an entertaining and educational podcast

Hi folks, We have a regular SPDX-legal call at the top of the hour (noon, Eastern time) at https://meet.jit.si/SPDXLegalMeeting We'll have a look at whatever needs attention to close out our "document

Hi all, I have recently joined the SPDX legal mailing list and wanted to give a short introduction. My name is Anna Haipola and I am a Legal Counsel supporting the Open Source Program Office at Nokia.

Dear all, I'm continuing with my travels tomorrow, and thus must unfortunately send my regrets for the SPDX Legal Team meeting. Hope to see you next month! Best wishes, Sebastian

Please see our first Change Proposal submission from Alexios here: https://github.com/spdx/change-proposal/blob/main/proposals/ExceptionRef.md This is a cross-team issue for tech and legal teams. Plea

Hi All, As per our discussion about collaboratively updating the License List FAQ, I created this Google doc, so multiple people can make changes/additions at the same time and review before we move t

Hi all, We have our regularly scheduled meeting tomorrow at 10 am mountain time (aka 9am Pacific time / noon eastern time). As we draw close to the end of this release cycle, let’s take an honest look

If at all possible, I'd like to have encoding too... -- 真実はいつも一つ！/ Always, there's only one truth!

Hello, I recently read a thread about someone asking about adding the Monkey's Audio codec to openSUSE and it having an odd license[1], and I was thinking of bringing this to Fedora as well. However,

Hi all, Sending a quick reminder that the SPDX Legal Team call will be starting shortly (at the top of the hour). We'll be focusing on the open documentation tasks for 3.19, to confirm on who is takin

Hi all, I just made a new issue to capture this, but wanted to raise it here for broader discussion. If we say that all OSI-approved are included on the SPDX License List, would we want to extend this

Hi all, just a quick reminder that the SPDX Legal Team call will be starting shortly. We'll be focusing on the following topics: * quick look at #1603 - x11vnc-openssl-exception * discuss release proc

Hi all, From our last call, the subject of 'when can people start using short ids? ‘ came up. This has been asked before on individual license submissions and we have answered informally, but it might

Just out of curiosity, has SPDX been requested to or considered assigning identifiers to artificial intelligence software licenses? I ran across the Stable Diffusion README, which contains the followi

Hi again, Now that 2.3 is out, this question is more pertinent: Note, if I want to link to a specific part of the SPDX spec, I can find it via the HTML format, for example: https://spdx.github.io/spdx

Dear SPDX community, As mentioned on a couple of the general calls some time ago, the Steering Committee has been working on a Change Proposal template and process to facilitate communication, priorit