On 3/14/23 10:04, Caolán McNamara wrote:
On Tue, 2023-03-14 at 08:47 -0500, Michael Catanzaro wrote:
... LibreOffice ...
FWIW I updated the LibreOffice one a while ago and ended up with:
MPL-2.0 AND Apache-2.0 AND LGPL-3.0-only AND LGPL-3.0-or-later AND CC0-
1.0 AND BSD-3-Clause AND (LGPL-2.1-only OR SISSL) AND (MPL-2.0 OR LGPL-
3.0-or-later) AND (MPL-2.0 OR LGPL-2.1-or-later) AND (MPL-1.1 OR GPL-
2.0-only OR LGPL-2.1-only)
Pardon the small digression...
One of the benefits of switching to this sort of license tag in the RPMs
is that it is purely objective fact; there are no subjective
determinations or opinions involved. So, for example, if that expression
above applies to the source tarball (or repository tag) for LibreOffice
7.5.2.1, that expression is not in any way specific to Fedora; it's the
same for everyone who consumes that source release, no matter how they
are packaging it.
This opens the door to sharing the burden across all those who consume
the source releases, and even reaching community consensus on what the
proper license expression is for any given source release, sharing that
expression with the upstream project so that it can be used by anyone
else in the future who needs it, and collaborative updates to the
expression when new source releases are made.
This was (and still is) the goal of the OSI's ClearlyDefined project:
community collaboration to produce consensus license expressions for a
given source artifact, including separation into facets (content which
ends up in the binaries, content which is used for build and/or test,
content which is documentation, etc.). It hasn't really taken off like
many had hoped it would, but it also hasn't died... it just needs more
large projects (like Fedora) to decide that it would be better for the
overall community if the results of the license scans were contributed
to a global database instead of just stored with the project's sources.
--
Kevin P. Fleming
He/Him/His
Principal Program Manager, RHEL
Red Hat US/Eastern Time Zone
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue