On Tue, Jul 30, 2024 at 11:22 AM Miroslav Suchý <msu...@redhat.com> wrote:
>
> Dne 30. 07. 24 v 4:40 odp. Miro Hrončok napsal(a):
>
> churchyard pypy pypy3.10 pypy3.9
>
>
> IMHO this uses a valid Callaway expression.
>
> It has UCD in it, which is not part of fedora-license-data, but it was listed 
> in the old wiki:
>
> There is https://fedoraproject.org/wiki/Licensing:UCD
>
> And it is listed in 
> https://fedoraproject.org/w/index.php?title=Licensing:Main&oldid=651191#Good_Licenses
>
> ---
>
> https://gitlab.com/fedora/legal/fedora-license-data/-/issues/30
>
> With last Richard comment from that issue I guess converting to Unicode-3.0 
> is the right step. Correct?

No, I think in context I was only commenting on the package
perl-Encode. Sorry, I see that is confusing in the issue comment
thread.

That issue does give some sense of the problem here, particularly this comment:
https://gitlab.com/fedora/legal/fedora-license-data/-/issues/30#note_1321684964

Still, Miro is correct, `UCD` is a valid Callaway abbreviation for a
license that was assumed to be "good" under the Callaway system. On
the other hand, any use of Callaway `UCD` is inherently problematic
because the Callaway classification doesn't really make any sense
under the principles underlying the Callaway system. I believe there
is another issue where I hypothesize that `UCD` was classified as
"good" because in possibly most cases where it seems to apply, the
license is bogus because the purportedly covered material is likely in
the public domain.

Richard

-- 
_______________________________________________
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

Reply via email to