From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] What should the default acceptable licenses be?
Date: Tue, 29 Jan 2019 13:27:30 -0500 [thread overview]
Message-ID: <CAGfcS_mBxYu4T4PAv2na_Nhsm6yVKR=67u_u6MHptyFmsnoRmg@mail.gmail.com> (raw)
In-Reply-To: <CAAr7Pr9fFWDPUiCwGFcetQXhX-uLNr6zr0NKkqHS1jJ5eqqNYA@mail.gmail.com>
On Tue, Jan 29, 2019 at 12:53 PM Alec Warner <antarus@gentoo.org> wrote:
>
> 1) Do the users not currently have a choice today? (e.g. do we need to populate the @nonfree license set?)
Since licenses are excluded by default I'm not sure if a non-free
explicit set helps much, but there is an EULA license group.
> I think if there isn't a @free-only (or -@nonfree) item we should do the work to make that possible (so ensure 1 is implemented.)
We have plenty of options here:
FREE-SOFTWARE
FREE
BINARY-REDISTRIBUTABLE
GPL-COMPATIBLE
FSF-APPROVED
OSI-APPROVED
MISC-FREE
(Just a selection.)
Everything is in profiles/license_groups
> I think a @free default fits right into the Gentoo Social Contract and while I oppose it on a personal basis (because I think the result harms users) I do support it on an organizational basis.
Not depending on non-free software sounds nice in principle until you
start talking about all those little things that make physical
hardware actually work. If it were a practical option I'd be all for
it. Otherwise this is a choice that really only exists on paper.
For seasoned users it isn't that big a deal since we mostly have our
own make.conf files and so on. I just am concerned it will be hard
for users.
What will we put in the handbook? Will we want to encourage them to
use a config that we know will often not work, or will we be up-front
that our defaults break most of the time in the real world? If we
have a default that often causes problems we should probably be pretty
up-front about that in the handbook so that users don't have to go to
#gentoo when their system breaks to find out that nobody actually
follows the official docs/defaults.
Honestly, though, Gentoo has for its entire history been about
practical defaults, and not about FSF/OSI purity. We certainly try
not to depend on non-free software as we say in our social contract,
but these issues are all way upstream of Gentoo. IMO we ought to be
finding a practical balance here and not be driven entirely by
ideology. Personally I'm a pretty big FSF fan in general, but I think
a distro needs to be practical first, with the option for purity, but
of course complying with redistribution restrictions.
--
Rich
next prev parent reply other threads:[~2019-01-29 18:27 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
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 [this message]
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='CAGfcS_mBxYu4T4PAv2na_Nhsm6yVKR=67u_u6MHptyFmsnoRmg@mail.gmail.com' \
--to=rich0@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