legal May 2023

legal@lists.fedoraproject.org

9 participants
14 discussions

Re: Changing the License tag of python-rpm-generators from GPLv2+ to a monstrosity

by Richard Fontana

On Fri, May 5, 2023 at 9:56 AM Chris Kelley <ckelley(a)redhat.com> wrote: > > As a purely logical expression, this simplifies to "GPL-2.0-or-later AND LGPL-2.1-or-later". Is that sort of simplification not allowed? The short answer is, these are not truly logical expressions and therefore they shouldn't necessarily simplify. Of course you could adopt some arbitrary convention for such simplification, which might or might not be well-grounded in some interpretation of the licenses at issue. In the past, there was no documented uniform set of conventions and basically each package maintainer applied their own assumptions about how license expressions could be simplified, leading to general inconsistency across different packages. The general trend in Fedora that I observed over many years was that license tags were getting more specific, i.e. less "simplification" was being done (or ignoring certain licenses was occurring less). This is actually shown by the fact that the Callaway system had a "Public Domain" which was widely used in packages with license tags containing references to other licenses. So we aren't actually changing policy here. Still, the cases involving public domain dedications are fairly extreme in this regard. If we *were* to adopt some system of simplification of license expressions that's probably where we'd start. Richard > > On Fri, 5 May 2023, 13:20 Miro Hrončok, <mhroncok(a)redhat.com> wrote: >> >> python-rpm-generators License tag changes from GPLv2+ to: >> >> GPL-2.0-or-later AND LGPL-2.1-or-later AND (LicenseRef-Fedora-Public-Domain OR >> LGPL-2.1-or-later OR GPL-2.0-or-later) >> >> https://src.fedoraproject.org/rpms/python-rpm-generators/pull-request/67 >> >> Funny thing is that the "(LicenseRef-Fedora-Public-Domain OR LGPL-2.1-or-later >> OR GPL-2.0-or-later)" thing was originally chosen to keep the License tag of >> the package simple while allowing others to grab the code from it without >> obligations :/ >> >> -- >> Miro Hrončok >

11 months, 2 weeks

1
0
0 / 0

Re: Changing the License tag of python-rpm-generators from GPLv2+ to a monstrosity

by Mamoru TASAKA

Chris Kelley wrote on 2023/05/05 22:55: > As a purely logical expression, this simplifies to "GPL-2.0-or-later AND > LGPL-2.1-or-later". Is that sort of simplification not allowed? > This is no longer allowed: https://docs.fedoraproject.org/en-US/legal/license-field/#_no_effective_l... Yes, so I am also re-checking the whole sources in the srpm I maintain... Regards, Mamoru > > On Fri, 5 May 2023, 13:20 Miro Hrončok, <mhroncok(a)redhat.com> wrote: > >> python-rpm-generators License tag changes from GPLv2+ to: >> >> GPL-2.0-or-later AND LGPL-2.1-or-later AND >> (LicenseRef-Fedora-Public-Domain OR >> LGPL-2.1-or-later OR GPL-2.0-or-later) >> >> https://src.fedoraproject.org/rpms/python-rpm-generators/pull-request/67 >> >> Funny thing is that the "(LicenseRef-Fedora-Public-Domain OR >> LGPL-2.1-or-later >> OR GPL-2.0-or-later)" thing was originally chosen to keep the License tag >> of >> the package simple while allowing others to grab the code from it without >> obligations :/ >> >> -- >> Miro Hrončok >> -- >> Phone: +420777974800 >> IRC: mhroncok >> _______________________________________________ >> devel mailing list -- devel(a)lists.fedoraproject.org >> To unsubscribe send an email to devel-leave(a)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/devel@lists.fedoraproject.org >> Do not reply to spam, report it: >> https://pagure.io/fedora-infrastructure/new_issue >> > > > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)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/devel@lists.fedoraproject.org > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

11 months, 2 weeks

2
1
0 / 0

Changing the License tag of python-rpm-generators from GPLv2+ to a monstrosity

by Miro Hrončok

python-rpm-generators License tag changes from GPLv2+ to: GPL-2.0-or-later AND LGPL-2.1-or-later AND (LicenseRef-Fedora-Public-Domain OR LGPL-2.1-or-later OR GPL-2.0-or-later) https://src.fedoraproject.org/rpms/python-rpm-generators/pull-request/67 Funny thing is that the "(LicenseRef-Fedora-Public-Domain OR LGPL-2.1-or-later OR GPL-2.0-or-later)" thing was originally chosen to keep the License tag of the package simple while allowing others to grab the code from it without obligations :/ -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

11 months, 2 weeks

1
0
0 / 0

"This document is placed in the public domain or under the CC0-1.0-Universal license, whichever is more permissive"

by Miro Hrončok

Hello, Python PEPs are licensed as: > This document is placed in the public domain or under the CC0-1.0-Universal > license, whichever is more permissive. How do I express this statement in a license field of a Fedora package, if the package includes a copy of the PEP text? Do I use: License: CC0-1.0 because "Public Domain" is discouraged? Or do I use: License: LicenseRef-Fedora-Public-Domain because Public Domain is more permissive? Or do I use: License: LicenseRef-Fedora-Public-Domain OR CC0-1.0 because the "whichever is more permissive" clause is to be determined by whoever wants to distribute/modify this and not by me? Or do I use something different entirely? --- Now suppose I have *a script* licensed like this. Do I make different choices because CC0-1.0 is not allowed for code? -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

11 months, 3 weeks

2
3
0 / 0

← Newer
1
2
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

legal May 2023