From: Ulrich Mueller <ulm@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-dev <gentoo-dev@lists.gentoo.org>,
licenses <licenses@gentoo.org>
Subject: [gentoo-dev] Re: [RFC] Adding 'GPL-2-only', 'GPL-3-only' etc. license variants for better auditing
Date: Sat, 21 Sep 2019 22:58:03 +0200 [thread overview]
Message-ID: <w6gblvdpdt0.fsf@kph.uni-mainz.de> (raw)
In-Reply-To: <c8f0dbac2310d90456ea17ecc50d79acbe82d50e.camel@gentoo.org> ("Michał Górny"'s message of "Sat, 21 Sep 2019 18:09:20 +0200")
[-- Attachment #1: Type: text/plain, Size: 1787 bytes --]
>>>>> On Sat, 21 Sep 2019, Michał Górny wrote:
> I'd like to propose to employ a more systematic method of resolving this
> problem. I would like to add additional explicit 'GPL-n-only' licenses,
> and discourage using short 'GPL-n' in favor of them. The end result
> would be three licenses per every version/variant, e.g.:
> GPL-2-only -- version 2 only
> GPL-2+ -- version 2 or newer
> GPL-2 -- might be either, audit necessary
To elaborate a bit more on this: "GPL-2" already has that well defined
meaning that your proposed "GPL-2-only" has, namely that the package is
licensed under the GNU General Public License, version 2.
Presumably, your change would cause a long transition time, in which we
would have *three* variants for every GPL version (as well as LGPL,
AGPL, FDL), two of them with identical meaning. And after the transition
time, we would have "GPL-2-only" instead of "GPL-2", which is not only
longer but also not accurate.
Plus, it would result in paradoxical entries like "|| ( GPL-2-only
GPL-3-only )" for a package that can be distributed under GPL versions 2
or 3 but no later version.
If the goal of this exercise is to do an audit of ebuilds labelled as
"GPL-2", then a less intrusive approach (which I had already suggested
when this issue had last been discussed) would be to add a comment to
the LICENSE line, either saying "# GPL-2 only" for packages that have
been verified. Or the other way aroung, starting with a comment saying
that it is undecided, which would be removed after an audit. This would
have the advantage not to confuse users, and have no impact on their
ACCEPT_LICENSE settings. (For example, some people exclude AGPL and
would have to add entries for AGPL-3-only.)
Ulrich
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-09-21 20:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-21 16:09 [gentoo-dev] [RFC] Adding 'GPL-2-only', 'GPL-3-only' etc. license variants for better auditing Michał Górny
2019-09-21 16:57 ` Matt Turner
2019-09-21 23:21 ` Matt Turner
2019-09-21 23:46 ` Ulrich Mueller
2019-09-22 0:03 ` Matt Turner
2019-09-24 3:45 ` Matt Turner
2019-09-24 7:13 ` Ulrich Mueller
2019-09-24 15:39 ` Matt Turner
2019-09-21 19:17 ` [gentoo-dev] " Ulrich Mueller
2019-09-21 19:26 ` William Hubbs
2019-09-21 19:57 ` Michał Górny
2019-09-21 22:45 ` William Hubbs
2019-09-22 6:12 ` Michał Górny
2019-09-24 1:42 ` Jason Zaman
2019-09-24 3:43 ` Matt Turner
2019-09-24 6:16 ` Ulrich Mueller
2019-09-21 19:56 ` [gentoo-dev] " Michael Orlitzky
2019-09-21 19:59 ` Michał Górny
2019-09-21 20:02 ` Michael Orlitzky
2019-09-21 20:58 ` Ulrich Mueller [this message]
2019-09-21 22:01 ` [gentoo-dev] " Matt Turner
2019-09-21 23:38 ` Ulrich Mueller
2019-09-22 9:16 ` Kent Fredric
2019-09-22 16:36 ` [gentoo-dev] " Richard Yao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=w6gblvdpdt0.fsf@kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=licenses@gentoo.org \
--cc=mgorny@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox