public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Haelwenn (lanodan) Monnier" <contact@hacktivis.me>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Should we allow "GPL, v2 or later" for ebuilds?
Date: Wed, 12 Feb 2020 05:37:34 +0100	[thread overview]
Message-ID: <20200212043734.GB29434@cloudsdale.the-delta.net.eu.org> (raw)
In-Reply-To: <CAGfcS_n_4TBiQ5sZ9MEkyefHyGg5OeqJm8K9LDsG0=W95dUA4Q@mail.gmail.com>

[2020-02-11 10:52:57-0500] Rich Freeman:
> On Tue, Feb 11, 2020 at 10:05 AM Haelwenn (lanodan) Monnier
> <contact@hacktivis.me> wrote:
> >
> > Maybe it could for now be a simple agreement on putting your code to
> > the Gentoo Foundation under the GPL-2+ but it would be published under
> > the GPL-{2,3,…}?
> >
> 
> Well, if we were going to get people to start signing things I suggest
> just sticking to the FLA since it actually was written by lawyers.

Absolutely, I misunderstood that the FLA wasn't ready at all, it's 
much better to have it instead.

> I attached a copy, but along these lines the key section is:
> We agree to (sub)license the Contribution or any Materials containing,
> based on or derived from your Contribution under the terms of any
> licenses the Free Software Foundation classifies as Free Software
> License and which are approved by the Open Source Initiative as Open
> Source licenses.
> 
> That is, Gentoo would control the licenses, but they would have to be
> FSF/OSI approved.  That doesn't mean that anybody could choose any
> FSF-approved license - Gentoo would still have to do the licensing.
> This is just a limitation on the grant of power from the original
> author to Gentoo on WHAT licenses GENTOO can choose.
> 
> There is also a variant of the FLA that can further narrow down the
> licenses that Gentoo gets to choose from, but IMO if you're going to
> go down this path it makes sense to keep things flexible.  We could of
> course just limit Gentoo to GPL v2+, and initially Gentoo does v2/3
> and later Gentoo could revise to any later version of the GPL.  But if
> for whatever reason the GPL falls out of favor then we can't adapt
> futher.
> 
> Ultimately though anything like this involves giving up control.

Which happens a lot when you have do to anything with others, and is
quite how using the internet and free software sounds like to me.

Anyway, this FLA document generator looks really good to me, much better 
than a weird "or later" on a license.
FSF/OSI sounds a bit too much flexible but personally I think I can 
trust gentoo enough to pick a similar license and otherwise it seems to 
restricts flexibility a bit too much. At least the option of GPL-2+ but 
with the change control put to gentoo would be possible.


  reply	other threads:[~2020-02-12  4:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-27 11:41 [gentoo-dev] Should we allow "GPL, v2 or later" for ebuilds? Ulrich Mueller
2020-01-27 11:52 ` Michał Górny
2020-01-27 12:15 ` Jonas Stein
2020-01-27 15:31 ` Rich Freeman
2020-01-30 11:20 ` Haelwenn (lanodan) Monnier
2020-01-30 13:19   ` Rich Freeman
2020-02-04  0:42     ` Kent Fredric
2020-02-11 15:05     ` Haelwenn (lanodan) Monnier
2020-02-11 15:52       ` Rich Freeman
2020-02-12  4:37         ` Haelwenn (lanodan) Monnier [this message]
2020-01-30 13:39 ` Hanno Böck
2020-01-30 14:23   ` 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=20200212043734.GB29434@cloudsdale.the-delta.net.eu.org \
    --to=contact@hacktivis.me \
    --cc=gentoo-dev@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