public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: bkuhn@sfconservancy•org (Bradley M. Kuhn)
To: linux-arm-kernel@lists•infradead.org
Subject: Would like to form a pool of Linux copyright holders for faster GPL enforcement against Anthrax Kernels
Date: Mon, 20 May 2013 11:13:00 -0400	[thread overview]
Message-ID: <87a9npvg5f.fsf@ebb.org> (raw)
In-Reply-To: <51973B45.7040209@gmail.com> (Eric Appleman's message of "Sat, 18 May 2013 04:26:45 -0400")

Eric Appleman wrote at 04:26 (EDT) on Saturday:
> Would anyone be interested in forming such a pool? I am willing to
> wait years for this to be resolved through certain organizations, but
> I believe we can do better.

As some on these lists likely already know, Conservancy's GPL Compliance
Project for Linux Developers [0] is aware of this matter and is
considering what actions to take, and how such actions should be ranked
in priority given the queue of the hundreds of known GPL violations on
Linux occurring every day.

We very much appreciate that Eric has brought the matter to our
attention and I'm continuing to correspond with Eric privately in the
hopes that we can resolve the matter.

If anyone wants to join Conservancy's GPL Compliance Project for Linux
Developers, please do contact me!

[0] More details on Conservancy's GPL Compliance Project for Linux
    Developers can be found at
    https://sfconservancy.org/news/2012/may/29/compliance/

Sincerely,
-- 
Bradley M. Kuhn, Executive Director, Software Freedom Conservancy

      reply	other threads:[~2013-05-20 15:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-18  8:26 Would like to form a pool of Linux copyright holders for faster GPL enforcement against Anthrax Kernels Eric Appleman
2013-05-20 15:13 ` Bradley M. Kuhn [this message]

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=87a9npvg5f.fsf@ebb.org \
    --to=bkuhn@sfconservancy$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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