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 Trustees <trustees@gentoo.org>
Subject: Re: [gentoo-project] Bad license and attribution by ChromiumOS and CoreOS
Date: Sat, 7 Mar 2015 07:09:13 -0500	[thread overview]
Message-ID: <CAGfcS_nR85riZuAGwy=6KS81j6Nc4uCkMHkc01mmzJfMbP06=g@mail.gmail.com> (raw)
In-Reply-To: <21754.48293.955801.232338@a1i15.kph.uni-mainz.de>

On Sat, Mar 7, 2015 at 3:53 AM, Ulrich Mueller <ulm@gentoo.org> wrote:
>
>> Since this is a copy of Gentoo ebuilds this is demonstrably wrong, the
>> copyrights on the files themselves are intact. Copyright is obviously
>> Gentoo Foundation, and license is GPL-2.
>
> Thanks for noticing this. Quoting the GPL-2:
>
>    4. You may not copy, modify, sublicense, or distribute the Program
>    except as expressly provided under this License.  Any attempt
>    otherwise to copy, modify, sublicense or distribute the Program is
>    void, and will automatically terminate your rights under this License.
>
> Does this apply here? It would mean that Google's rights to distribute
> the Portage tree have been terminated.

I'd probably talk to a lawyer before celebrating the death of Google.

All the copyright notices in the files are intact.  As far as I can
tell Google hasn't done anything that actually violates the GPL.  The
only complaint here is that there is a readme file with a different
copyright notice inside.  The issue is trivially correctable by Google
by simply fixing the notice, or clarifying what it applies to.  No
court is going to prefer permanently terminating Google's rights to
distribute ChromeOS over simply letting them clean things up.

Besides, is the goal of Gentoo really to kill off the #1 used open
source desktop OS in the world which is based on Gentoo?  That hardly
sounds like "Gentoo lives for the community, by the community" as
stated in the Foundation's charter.  The purpose of our copyrights is
to preserve Gentoo so that all can benefit from it, not to club people
over the head with if they dare to actually use Gentoo and make a
mistake.

Honestly, I'm a bit concerned by some of the talk in this thread.
What kind of message to we want to send to companies or organizations
that use Gentoo?  Do we really want the message to be "better not slip
up, because Gentoo is the kind of group that will get your site taken
down on a weekend over a readme file?"  Don't get me wrong - I think
Google has benefitted a great deal from Gentoo and I'd love to see
they contribute back more actively than they already do (we do have
people doing 10% time work for Gentoo and we have benefitted from past
GSoC).

How would we want to be treated in the reverse situation?  I was
annoyed when it seemed like everybody was over-reacting over the eudev
copyright notice fiasco.  Copyright is complicated, and most people
working on software are not lawyers, and since there isn't a ton of
open source case law even the lawyers can disagree on where the lines
are.  When somebody infringes on your copyright the solution is to
work with them to fix things, so that the scope of open source
software is increased and the public benefits, not to act like the
RIAA.  Since we are an open community, we make our mistakes in the
public light - we should afford the same leniency to others since we
WANT others to act as open communities as well.

I'm sure if we ask Google nicely to clean things up they will.  That
is the best outcome for the general public, and the best outcome for
Gentoo.  Remember, we can borrow their code as well, and some of our
devs do just that.  If we have trouble getting through to them the
legal issues would allow us to escalate things, but that can be done
in a way that creates opportunities ("hey, while we have you on the
phone, did you realize how much you benefit from Gentoo, and are there
ways we can better partner to improve things for all of our users?").
Why make enemies when we can make friends?

-- 
Rich


  parent reply	other threads:[~2015-03-07 12:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-07  2:22 [gentoo-project] Bad license and attribution by ChromiumOS and CoreOS Patrick Lauer
2015-03-07  3:46 ` Alex Brandt
2015-03-07  3:55 ` Andrew Savchenko
2015-03-07  4:13   ` Rich Freeman
2015-03-07 13:44     ` Sven Vermeulen
2015-03-07  8:53 ` Ulrich Mueller
2015-03-07  9:05   ` Andrew Savchenko
2015-03-07 12:09   ` Rich Freeman [this message]
2015-03-07 14:27     ` Anthony G. Basile
2015-03-22  7:36       ` Jeroen Roovers
2015-03-22  8:21         ` Ulrich Mueller
2015-03-22 12:14           ` Rich Freeman
2015-03-22 16:22             ` Ulrich Mueller
2015-03-22 16:25           ` Mike Frysinger
2015-03-22 18:08             ` Ulrich Mueller
2015-03-11  6:11     ` Mike Frysinger
2015-03-07  9:33 ` Matthias Maier
2015-03-07 19:11 ` [gentoo-project] " Alec Warner
2015-03-11  5:22   ` Andrew Savchenko
2015-03-11  8:32     ` Kristian Fiskerstrand
2015-03-13  0:37   ` Alec Warner
2015-03-13  4:41 ` [gentoo-project] " Mike Frysinger
2015-03-13  7:46   ` Alexander Berntsen
2015-03-13 10:30   ` Andrew Savchenko
2015-03-13 11:26     ` Rich Freeman
2015-03-13 22:17       ` Rich Freeman
2015-03-13 22:29         ` Andrew Savchenko

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_nR85riZuAGwy=6KS81j6Nc4uCkMHkc01mmzJfMbP06=g@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=trustees@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