the full 15' sounds great, as I think all will be interested in the context as well thanks and look forward to it! Jilayne

Hi all, We have our regularly scheduled call tomorrow, Thursday at 10 am mountain standard time. (the US has now pushed our clocks forward, so we should be back to our normal time zone gap differences

Hi Neal, I made an issue for a new license request - https://github.com/spdx/license-list-XML/issues/1355 In the future, please submit a new licenses to be added to the SPDX License List via the Githu

Thanks Warner! "standard header" is narrowly defined in the context of the SPDX License List - https://github.com/spdx/license-list-XML/blob/master/DOCS/license-fields.md I am not sure where the FSF s

And I was just about to send out a reminder of our legal call in about an hour, so here's the reminder for everyone else! Thanks Vicky for letting us know and good luck with the deadline! - Jilayne

Hi all, We have some text at the bottom of this page https://spdx.dev/ids/ regarding the use of SPDX ids related to a recommendation about using and retaining standard headers when using/adding an SPD

Hi all, I came across a "variant" of the Caldera license. Here is what we have on SPDX: https://spdx.org/licenses/Caldera.html But this project - http://heirloom.sourceforge.net/sh.html has this licen

Hi Pierre, I am moving the general SPDX list to BCC and sending this via the SPDX legal list, as that is the right place for this question! Also not - I have approved your message and copied you here

Hi all, We have our regularly scheduled call today in a bit over an hour from now. We’ll get back to reviewing issues and prepping for the next release - as well as any updates on other on-going proje

Hi all, We have our regular call today at noon EDT. We'll catch up on any other "intros"; I think Warner was going to give an update on the SPDX work in FreeBSD (if you are ready to do so), and get or

Hi Karsten, well, I suppose that is not surprising it came up again, as I think we talked about some documentation during the last conversation, but, um, that never got done. Probably a good time to r

HI Karsten, I thought we discussed this or something very similar during the early licensing-profile discussions regarding a “distributed license” concept and it was put to rest? :) In any case, I thi

Hi all, Just a reminder of our regularly scheduled call in a bit over an hour. The docfest is going on today as well, so we may have thinner attendance, but we’ll meet and work on looking at issues an

Hi OSI, Just noting that this does not appear to be on the SPDX License List currently. Copying SPDX-legal here as well. A new license request has been added here: https://github.com/spdx/license-list

Hi all, Just a reminder we have our legal call tomorrow/Thursday at the usual time and place. https://meet.jit.si/SPDXLegalMeeting Paul and I both have a conflicts, but Steve will there. Now that we h

Hi all, Thanks for the quick feedback and I'm glad to see that we basically all seem to agree that, yes, the SPDX License List should have enough coverage of licenses that a free/open operating system

Hi all, I wanted to raise a question I've been thinking of in light for Fedora and other open source OS distros looking to adopt use of SPDX license identifiers in various ways. One concern that has b

Hi Sebastian, I knew/hoped there'd be some SPDX'ers who were also Fedora fans! See comment below on where folks familiar with SPDX could be of most help: For any of the licenses marked as "NO" (not on

Hi all, Sorry for the delay in responding, I got busy with other things and needed some time to fully re-read this thread and absorb everything. Thanks to Max, Matija, and Sebastian for your combined

Hi Anthony, Thanks for pointing this out. I tried to add a comment, but it appears to be closed. Thomas is active in the SPDX-tech team, but would be nice if someone from the SPDX-legal could add a bi