From: Ulrich Mueller <ulm@gentoo.org>
To: Alec Warner <antarus@gentoo.org>
Cc: gentoo-nfp <gentoo-nfp@lists.gentoo.org>
Subject: Re: [gentoo-nfp] Social contract and its effect on upstream software choices
Date: Fri, 01 May 2020 12:34:13 +0200 [thread overview]
Message-ID: <uwo5wosey@gentoo.org> (raw)
In-Reply-To: <CAAr7Pr-yA6rPp21TKfhr=YOpQM5vb5maO=axqBDG4qr=DM5htA@mail.gmail.com> (Alec Warner's message of "Thu, 30 Apr 2020 23:11:06 -0700")
[-- Attachment #1: Type: text/plain, Size: 1727 bytes --]
>>>>> On Fri, 01 May 2020, Alec Warner wrote:
> Consider a case where we have a piece of software and its open source.
> The open source software has various plugins, some of which look
> useful and we may wish to deploy them for Gentoo. However, we must
> consider the social contract, hence this discussion.
> Can we use the plugins if:
> (1) They are closed source (e.g. upstream provides binaries only with
> a restricted non-free license.)
IMHO it would contradict the Social Contract:
"However, Gentoo will never depend upon a piece of software or metadata
unless it conforms to the GNU General Public License, the GNU Lesser
General Public License, the Creative Commons - Attribution/Share Alike
or some other license approved by the Open Source Initiative (OSI)."
> (2) They are free software (e.g. FSF / OSI approved license) but they
> cost money.
No problem there. Also, we can freely redistribute them if they are free
software.
> (b) A subset, its free software and it costs money but it is free
> for open source communities to use.
Same as (2).
> (3) They are open source, but not free (e.g. they have some kind of
> open license but are not FSF / OSI approved.)
"Open source" has a well defined meaning. If the software is under an
open source license (i.e., a license in our @FREE group) then I don't
see any difference to (2).
OTOH, if they're only "free as in beer" then pretty much the same
argument as for (1) applies.
> (4) They are open source (and free), but we have chosen to use the
> built plugins (rather than building from source) for the sake of time
> and convenience.
That's not the Gentoo way of doing things. However, I don't see a
problem with the Social Contract.
Ulrich
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]
next prev parent reply other threads:[~2020-05-01 10:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 6:11 [gentoo-nfp] Social contract and its effect on upstream software choices Alec Warner
2020-05-01 10:34 ` Ulrich Mueller [this message]
2020-05-01 10:39 ` Michał Górny
2020-05-01 10:56 ` Ulrich Mueller
2020-05-04 10:07 ` Francisco Blas Izquierdo Riera (klondike)
2020-05-04 11:37 ` Roy Bamford
2020-05-04 12:25 ` Rich Freeman
2020-05-05 8:46 ` Michał Górny
2020-05-05 16:13 ` Alec Warner
2020-05-05 16:29 ` Raymond Jennings
2020-05-05 18:57 ` Rich Freeman
2020-05-06 1:25 ` Denis Dupeyron
2020-05-06 2:04 ` Rich Freeman
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=uwo5wosey@gentoo.org \
--to=ulm@gentoo.org \
--cc=antarus@gentoo.org \
--cc=gentoo-nfp@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