I am preparing to update a batch of packages’ License tags to SPDX, with License field changes as reported below.
----------------------------------------
The License field for the agenda package will be updated from an effective license “GPLv3+” to “GPL-3.0-or-later AND GPL-2.0-or-later AND CC0-1.0”. The portion covered by CC0-1.0 is the AppData XML file, which is content.
----------------------------------------
The License field for the appeditor package will be updated from an effective license “GPLv3” to “GPL-3.0-only AND CC0-1.0”. The portion covered by CC0-1.0 is the AppData XML file, which is content.
----------------------------------------
The License field for the arpwatch package will be updated from “BSD with advertising”—which should have been just “BSD”—to “BSD-3-Clause”.
----------------------------------------
The License field for the c4core package will be updated from “MIT and Boost” to “MIT AND BSL-1.0”.
----------------------------------------
The License field for the c4project package will be updated from “MIT and ASL 2.0” to “MIT AND Apache-2.0”.
----------------------------------------
The License field for the cairomm and cairomm1.16 packages will be updated from “LGPLv2+” to “LGPL-2.0-or-later”.
----------------------------------------
The License field for the casc package will be updated from “LGPLv2+” to “LGPL-2.1-or-later”.
----------------------------------------
The License field for the cpp-hocon package will be updated from “ASL 2.0” to “Apache-2.0”.
----------------------------------------
The License field for the debugbreak package will be updated from “BSD” to “BSD-2-Clause”.
----------------------------------------
The License field for the dippi package will be updated from “GPLv3+”—which should have been just “GPLv3”—to “GPL-3.0-only AND CC0-1.0”. The portion covered by CC0-1.0 is the AppData XML file, which is content.
----------------------------------------
The License field for the dr_libs package will be updated from “Unlicense or MIT-0” to “Unlicense OR MIT-0”
----------------------------------------
The License field for the edac-utils package will be updated from “GPLv2+” to “GPL-2.0-or-later”.
----------------------------------------
The License field for the fast_float package will be updated from “ASL 2.0 or MIT” to “Apache-2.0 OR MIT”.
----------------------------------------
The License field for the festival-freebsoft-utils package will be updated from “GPLv2+” to “GPL-2.0-or-later”. Furthermore, the License field for the festival-freebsoft-utils-doc subpackage, previously inherited from the base package, will be updated and corrected to reflect its dual-licensed status: “GPL-2.0-or-later OR GFDL-1.2-no-invariants-or-later”.
----------------------------------------
The License field for the fflas-ffpack package will be updated from “LGPLv2+” to “LGPL-2.1-or-later AND LGPL-2.0-or-later”.
----------------------------------------
The License field for the flatbuffers package will be updated and corrected from “ASL 2.0 and BSD” to “Apache-2.0”.
The code previously considered BSD (BSD-3-Clause) is that which is derived from grpc, which has an upstream license of BSD-3-Clause. It is now clear that even code from grpc is intended to be Apache-2.0 in this project. (Google is the copyright holder for both projects, so it can relicense at will.) See https://github.com/google/flatbuffers/pull/7073.
----------------------------------------
The License field for the flintqs package will be updated from “GPLv2+” to “GPL-2.0-or-later”.
----------------------------------------
The License field for the fmidi package will be updated from “Boost” to “BSL-1.0”.
----------------------------------------
The License field for the freexl package will be updated from “MPLv1.1 or GPLv2+ or LGPLv2+” to “MPL-1.1 OR GPL-2.0-or-later OR LGPL-2.1-or-later”.
----------------------------------------
– Ben Beasley
Do Callway > SPDX license changes where there's a clear mapping and no other additions or removals still have to be announced? That wasn't my understanding. -- Thanks,
Maxwell G (@gotmax23) Pronouns: He/Him/His
On Mon, Aug 1, 2022 at 1:51 PM Maxwell G gotmax@e.email wrote:
Do Callway > SPDX license changes where there's a clear mapping and no other additions or removals still have to be announced? That wasn't my understanding.
My understanding of this rule/expectation is that it does not have anything directly to do with how the License: field is populated. Rather, it's to notify the Fedora community about a substantive upstream license change.
The new documentation says that there is supposed to be an announcement on both devel and legal. I have seen such announcements on devel before (in browsing list archives once in a blue moon) but I am not sure I've ever seen any on legal. I am not sure how important it is to preserve this rule at all, or to include both mailing lists, but I understood us to be retaining a rule that at least in theory previously existed.
Richard
On 8/1/22 11:50 AM, Maxwell G wrote:
Do Callway > SPDX license changes where there's a clear mapping and no other additions or removals still have to be announced? That wasn't my understanding.
no, updating existing packages to SPDX license identifiers does not need to be announced here. Nonetheless, thanks for sharing Ben! It's interesting and a bit helpful to see some examples!
Jilayne
-- Thanks,
Maxwell G (@gotmax23) Pronouns: He/Him/His
legal mailing list -- legal@lists.fedoraproject.org To unsubscribe send an email to legal-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/legal@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure