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

2023-05-05 Thread Richard Fontana
On Fri, May 5, 2023 at 9:56 AM Chris Kelley  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,  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
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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


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

2023-05-05 Thread Chris Kelley
How fun! Thanks for the links and explanation.

On Fri, 5 May 2023 at 16:09, Miro Hrončok  wrote:

> On 05. 05. 23 16:28, Mamoru TASAKA wrote:
> > 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_license_analysis
>
> Also
>
> https://docs.fedoraproject.org/en-US/legal/license-field/#_combined_disjunctive_and_conjunctive_license_expressions
> which says:
>
> """
> The license expression must reflect the disjunctive license choice even if
> one
> or both of the license identifiers in the OR expression also appear
> separately
> in the composite license expression.
>
> ...
>
> License: (GPL-3.0-or-later OR MPL-1.1) AND GPL-3.0-or-later AND MIT
>
> Here we repeat GPL-3.0-or-later because for one binary component it
> appears as
> part of an OR subexpression. That is, OR expressions must be treated as
> though
> they were a single distinct license.
> """
>
> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
>
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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


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

2023-05-05 Thread Miro Hrončok

On 05. 05. 23 16:28, Mamoru TASAKA wrote:

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_license_analysis


Also 
https://docs.fedoraproject.org/en-US/legal/license-field/#_combined_disjunctive_and_conjunctive_license_expressions 
which says:


"""
The license expression must reflect the disjunctive license choice even if one 
or both of the license identifiers in the OR expression also appear separately 
in the composite license expression.


...

License: (GPL-3.0-or-later OR MPL-1.1) AND GPL-3.0-or-later AND MIT

Here we repeat GPL-3.0-or-later because for one binary component it appears as 
part of an OR subexpression. That is, OR expressions must be treated as though 
they were a single distinct license.

"""

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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


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

2023-05-05 Thread 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_license_analysis

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,  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@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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


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

2023-05-05 Thread Chris Kelley
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?



On Fri, 5 May 2023, 13:20 Miro Hrončok,  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@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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


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

2023-05-05 Thread 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
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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