public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-project] eudev project announcement
Date: Sat, 15 Dec 2012 07:48:29 -0500	[thread overview]
Message-ID: <CAGfcS_n5FH+m4Duk9zBzaTE4Y21by9DLCPUM58dcRwJh=246eQ@mail.gmail.com> (raw)
In-Reply-To: <50CBF400.2060104@gentoo.org>

On Fri, Dec 14, 2012 at 10:52 PM, Richard Yao <ryao@gentoo.org> wrote:
>         The systemd developers were in the middle of a transition to the LGPL
> from the GPL when we forked. We inherited the code in the middle of that
> transition and we see no reason to pursue a different course. Therefore,
> all future changes that we make to eudev will be available under the LGPL.

Not sure what the driver is to use LGPL, but in general the Gentoo
social contract requires that all contributions be made under GPLv2+
or the CC BY-SAv2+.  I'm sure exceptions can be made if they make
sense and are aligned with Gentoo's mission (likely something that
would fall on the Foundation to approve).  If eudev were a non-Gentoo
project then Gentoo could depend on it as long as it used any
OSI-approved license.

Why not just use GPLv2+?  The LGPL is compatible, so this would not
prevent us from merging udev changes.

Not suggesting that we shouldn't use the LGPL if there is a good
reason to do so that is aligned with Gentoo's mission.  I would just
like to understand the reason for it.

Rich


  reply	other threads:[~2012-12-15 15:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-15  3:52 [gentoo-project] eudev project announcement Richard Yao
2012-12-15 12:48 ` Rich Freeman [this message]
2012-12-15 20:21   ` Richard Yao
2012-12-15 20:33 ` Samuli Suominen

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_n5FH+m4Duk9zBzaTE4Y21by9DLCPUM58dcRwJh=246eQ@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@lists.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