From: Alec Warner <antarus@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] What should the default acceptable licenses be?
Date: Sat, 26 Jan 2019 20:25:42 -0500 [thread overview]
Message-ID: <CAAr7Pr-R3EvOBMNAEiL7h8uge1reTiDRvPSTrVpCKL8R2cj-Cg@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_=CfxUf_-Zhjv8WPt1r=QSfRD=DgGX4045E3LqpdLG5KA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2394 bytes --]
On Sat, Jan 26, 2019 at 5:52 PM Rich Freeman <rich0@gentoo.org> wrote:
> On Sat, Jan 26, 2019 at 4:04 PM Kristian Fiskerstrand <k_f@gentoo.org>
> wrote:
> >
> > My personal opinion is we should have a default accepting FSF and OSI
> > approved free/libre licenses and require acceptance for anything else
> > though package.license / ACCEPT_LICENSE.
>
> From a practical standpoint is this going to block anything used on
> our stage3s or boot CDs needed for hardware support, such as firmware
> blobs/etc? I imagine most packages like this would not have
> FSF/OSI-approved licenses. That includes linux-firmware.
>
I think the stage3 is already pretty minimal anyway, I'd be curious about
what it would lose if we did this.
>
> I'm not sure if those are installed by default or how essential they
> are to actually boot/use any common hardware.
>
I want to avoid having a singular product here. I think ::gentoo is the
repo that is the metadistribution and we can basically have defaults there.
Consumers of ::gentoo are expected to tweak it. I think this is different
than say, a liveDVD image. The latter we don't expect users to tweak before
using and we should be trying to support normal use cases. If we need to
use non-free firmware to do it, I expect us to do that so that users who
boot the media actually get a working Gentoo install.
So I don't buy an argument that "Gentoo" as a whole has to do a particular
thing. I expect this discussion is actually more about "the Gentoo repo"
than about any particular shipped media. Maybe I'm misunderstanding things
though.
>
> Aside from this, Gentoo has always been more about pragmatism when it
> comes to licensing. We certainly make it easy to restrict licenses
> and have a pure-free system, but I'm not sure how painful it would be
> for users to have this be a default.
>
> In particular how likely is this to cause users to end up doing a
> substantial rebuild 5 minutes after booting their stage3 just to get
> the system back to a more "practical" state? Granted, bindist
> probably already causes these sorts of issues but we have no choice
> there.
>
I take the Bezos approach here. There are 2 types of decisions: reversible
and irreversible. This is a reversible decision pretty much, so its low
risk. If we change the default and the world starts to hate us, we can just
change it back.
-A
>
> --
> Rich
>
>
[-- Attachment #2: Type: text/html, Size: 3461 bytes --]
next prev parent reply other threads:[~2019-01-27 1:26 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 ` [gentoo-project] " Michał Górny
2019-01-26 22:51 ` Rich Freeman
2019-01-27 1:25 ` Alec Warner [this message]
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=CAAr7Pr-R3EvOBMNAEiL7h8uge1reTiDRvPSTrVpCKL8R2cj-Cg@mail.gmail.com \
--to=antarus@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