From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] What should the default acceptable licenses be?
Date: Sat, 26 Jan 2019 23:12:35 +0100 [thread overview]
Message-ID: <1548540755.2778.10.camel@gentoo.org> (raw)
In-Reply-To: <e2d92c1c-f129-6c45-becf-6ad48387bf17@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1959 bytes --]
On Sat, 2019-01-26 at 22:04 +0100, Kristian Fiskerstrand wrote:
> I would like to point the community at the following bug
> https://bugs.gentoo.org/676248:
> Bug 676248 - non-free licenses are accepted without user prompt
>
> In summary the question is whether non-free licenses should be accepted
> by default in Gentoo. today only licenses requiring EULA are not
> accepted by default. So this is a good opportunity to discuss whether we
> should deviate substantially from other distros like Debian.
>
I think the key point in this discussion is: what is the reason for this
change? Is it ideological ("because RMS tells us it's bad")? Is it
copycat rationale ("because Debian does it")? Or do you have any
specific practical implications to support this? (They should really be
listed in this thread! Otherwise this really feels like it's a change
requested to suit somebody's fancy).
My personal opinion is that our default ACCEPT_LICENSE should be a safe
default for our users. Not because they could get impure with non-free
software but because we don't want them to fall into pitfalls created by
restrictive licenses.
Most notably, we don't want to require users to verify whether they are
allowed to use the program they've just installed, or whether they can
build it with custom patches. If this change intends to help with this,
I'm for it.
However, I really do think you should clearly define the goals. For
example, are you going 'free' to the point of defaulting to USE=bindist?
Also, what about restrictive 'free' licenses that can actually get
people into trouble, like AGPL? I personally don't think it should be
allowed by default. Given the recent example, we don't want people
getting into trouble by upgrading berkdb on their systems, if they just
happen to use it and don't know the upgrade requires them to change
their online applications.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2019-01-26 22:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 21:04 [gentoo-project] What should the default acceptable licenses be? Kristian Fiskerstrand
2019-01-26 21:32 ` [gentoo-project] " Chí-Thanh Christopher Nguyễn
2019-01-27 9:47 ` Ulrich Mueller
2019-01-26 21:45 ` Thomas Deutschmann
2019-01-26 22:12 ` Michał Górny [this message]
2019-01-26 22:51 ` [gentoo-project] " Rich Freeman
2019-01-27 1:25 ` Alec Warner
2019-01-28 22:27 ` Matt Turner
2019-01-29 16:54 ` Thomas Deutschmann
2019-01-29 17:28 ` Brian Evans
2019-02-05 20:03 ` Roy Bamford
2019-01-29 17:53 ` Alec Warner
2019-01-29 18:27 ` Rich Freeman
2019-01-29 18:41 ` Kristian Fiskerstrand
2019-01-29 18:56 ` Kristian Fiskerstrand
2019-01-30 0:12 ` Thomas Deutschmann
2019-01-30 0:35 ` Alec Warner
2019-01-29 17:53 ` Rich Freeman
2019-01-31 16:53 ` Matt Turner
2019-02-05 23:47 ` [gentoo-project] " Kristian Fiskerstrand
2019-02-12 19:40 ` Alec Warner
2019-02-13 9:34 ` Thomas Deutschmann
2019-02-13 9:50 ` Kristian Fiskerstrand
2019-02-13 10:44 ` Ulrich Mueller
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=1548540755.2778.10.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-project@lists.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