legal February 2023

legal@lists.fedoraproject.org

14 participants
13 discussions

What license for sgp4
by Mattia Verga 13 Feb '23

13 Feb '23

SGP4 is a small C++ library which is bundled in python-sgp4 currently under review [1]. The source code is available from https://celestrak.org/publications/AIAA/2006-6753/ and in the FAQ it says: """ Are there any Licenses required to use the SGP4 code? There is no license associated with the code and you may use it for any purpose—personal or commercial—as you wish. We ask only that you include citations in your documentation and source code to show the source of the code and provide links to the main page, to facilitate communications regarding any questions on the theory or source code. """ Is there a license that fits? It seems some sort of Public Domain with attribution... Mattia [1] https://bugzilla.redhat.com/show_bug.cgi?id=2156932

2 1

ASL 2.0 with 'CUPS' exception when packaging libcupsfilters (reviving old 'ASL 2.0 with exceptions' thread)
by Zdenek Dohnal 13 Feb '23

13 Feb '23

Hi all, I'm about to put a new package - libcupsfilters - under review to get it into Fedora. It has the same license as CUPS - ASL 2.0 with exception, which was taken from LLVM and we talked about it in thread mentioned in subject. Now I checked https://docs.fedoraproject.org/en-US/legal/allowed-licenses/ and I see there Apache-2.0 WITH LLVM-exception, which matches the contents of the license and exception, but the name of the exception in the NOTICE file is 'CUPS exception'. Is it okay from legal part to use SPDX name ' Apache-2.0 WITH LLVM-exception' or do we need a special name? Thank you in advance! Zdenek -- Zdenek Dohnal Software Engineer Red Hat, BRQ-TPBC

2 2

Licenses without SPDX expression found in sane-frontends
by Zdenek Dohnal 09 Feb '23

09 Feb '23

Hi all, ppisar was doing the license review of the package when it arrived into EPEL 9 and proposed to update the SPEC file to the latest FPG. Since Fedora Licensing now requires SPDX names for licenses, he found two of them without SPDX name in sane-frontends: GPL-2.0-or-later WITH Autoconf-exception-2.0-like exception GPL-2.0-or-later WITH gnu-javamail-exception-like exception The former is used in config.guess+config.guess files generated Autoconf, the latter is a license which is used in SANE project. Would it be possible to review the licenses and assign a SPDX identifiers for them? Or make an agreement to use just GPL-2.0-or-later? Thank you in advance! Zdenek -- Zdenek Dohnal Software Engineer Red Hat, BRQ-TPBC

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

legal February 2023