public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: trustees@gentoo.org
Subject: Re: [gentoo-project] Bad license and attribution by ChromiumOS and CoreOS
Date: Sat, 7 Mar 2015 06:55:34 +0300	[thread overview]
Message-ID: <20150307065534.681790ffb1cd1c643ed9351b@gentoo.org> (raw)
In-Reply-To: <54FA60C8.2020503@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]

On Sat, 07 Mar 2015 10:22:00 +0800 Patrick Lauer wrote:
> Good $timezonegreeting,
> 
> The README at both
> 
> https://github.com/coreos/portage-stable
> and
> https://chromium.googlesource.com/chromiumos/overlays/portage-stable/+/master/README
> 
> claims that:
> 
> """
> Copyright (c) 2011 The Chromium OS Authors. All rights reserved.
> Use of this source code is governed by a BSD-style license that can be
> found in the LICENSE file.
> """
> 
> 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.
> 
> I have been unable to find a proper contact for both repositories, so I
> hope people that know who to contact are reading this.

1. Maybe a license and copyright violation claims should be filed
directly to github? They should contact upstream fast.

2. One may contact person responsible to that commit of invalid
README file:

Darin Petkov <petkov@chromium.org>
https://github.com/coreos/portage-stable/commit/0465d53c7be43d55cfabb3dff56f32803719d0fe
https://codereview.chromium.org/6756045

> Once this is corrected I'd strongly suggest to both downstreams to poste
> a prominent notice to inform all downstream users of this issue to avoid
> accidental license violations.

Best regards,
Andrew Savchenko

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2015-03-07  3:55 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 [this message]
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
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=20150307065534.681790ffb1cd1c643ed9351b@gentoo.org \
    --to=bircoph@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