On a related question, there's several licenses that are close to the public domain. Eg: "THE BEER-WARE LICENSE" (Revision 42): <phk@...> wrote this file. As long as you retain this notice you can do

I support the idea of Mike. In particular, this would help for both use and license compliance in (most) European countries. Please note that in many countries there is no "public domain" in

Thanks for the clarification Jilayne! If the idea is to collect information about the different forms used to say "this is in the public domain" with an eye towards option 3, then yes, I think your

Yocto Project ran into this in a single case in our core layer for a single file which was listed as "PD". This was the one source file we couldn't therefore put an SPDX license identifier on. After

Thanks for the quick responses, Steve and Mike! I should have been more clear on what I needed input on ASAP - which was, a) what info would be helpful to collect (now) about any public domain

In addition to Steve's thoughts... I will respond quickly as that was the request ... and likely miss issues. My only additional though is could we add a generic public domain license reference to the

Hi Jilayne, since you asked for input ASAP, here are a few immediate gut reactions :) I think getting the data of seeing a bunch of different ways that people said "this code is released into the

Hi SPDX-legal, I have raised this a couple times in the past few months or so, but now that it is more of a "ripe" topic, I wanted to get some input on preliminary ideas:

Hello all, The version 3.18 release of the license list is now tagged and live at https://spdx.org/licenses. 10 new licenses / exceptions were added to the

Hi all, Just a last minute reminder of our regular call today at the top of the hour. As mentioned previously, for the next release cycle (through end of Sept) we are going to focus on updating and

I've thought some more about certain unintended problems some of us were previously discussing regarding the use of SPDX-License-Identifier: in source files. In particular it's occurred to me that the

I hope you are all ready for the upcoming pains in the next few years. Transitioning Fedora to SPDX is not going to be a happy time for a little while, since there's a huge impedance mismatch between

Nice. This certainly makes it easy to map from Fedora to SPDX IDs! SPDX license identifiers have emerged as a standard Woo hoo! From:Spdx-legal@... <Spdx-legal@...> on behalf of Steve

Hi all, On our call a few days ago, Steve raised the idea of using the next release to JUST focus on documentation improvements. There haven’t been a ton of new license requests and some of the

Hi all, I just went through all the issue in terms of what we can likely get in for the 3.18 release. Seems like most issues are already assigned to Steve or I :) Could someone pick up this one and

Jilayne, this is awesome news -- thanks for passing it along! Looking forward to us working with the Fedora community to support them adding SPDX license IDs across the distro. Steve

Hot off the press! Link to blog post of this here:https://communityblog.fedoraproject.org/important-changes-to-software-license-information-in-fedora-packages-spdx-and-more/

Hi all, Just a quick reminder that the SPDX-legal call will be at the top of the hour. We'll focus on what tasks can be completed for the next release and, if

Greetings all, The SPDX spec version 2.3 is now available for review at https://spdx.github.io/spdx-spec/v2.3-RC1/. A summary of the changes can be found in the SPEC Annex I. If you

Hi Max, Given the evolution of the SPDX Specification format(s) - that is, it was mainly in .pdf form for most of the past versions, I’d say that if you want to refer to a specific version, I’d