From: Eric Appleman <erappleman@gmail.com>
To: linux-arm-msm@vger.kernel.org
Cc: linux-arm-kernel@vger.kernel.org
Subject: Would like to form a pool of Linux copyright holders for faster GPL enforcement against Anthrax Kernels
Date: Sat, 18 May 2013 04:21:13 -0400 [thread overview]
Message-ID: <519739F9.7020508@gmail.com> (raw)
Background on Anthrax Kernels and their GPL violation:
http://pastebin.com/X5Cciy03
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.
Last I checked, I have 1 long-time poster of the gpl-violations list on
board. Would anyone else like to join? Ideally I'd like to get the LKML
(which I have CC'd among others) involved so that authors of critical
Linux components be a part of this. I'm not sure if my defconfig commits
to Android kernel branches count as contributions, so I'm not going to
consider myself a Linux contributor unless told otherwise.
This pool would be used in the following manner:
* Formally requesting source for binaries (means to request source is
actively hidden)
* Formally requesting removal of critical copyrighted code that Linux
cannot function without
* Informing interested parties with respect to refusals of the above
The CTO of Anthrax's hosting server is very interested in terminating
Chad Goodman's account. Bullet point #3 might come into effect here.
If this is a bad idea, breaks list etiquette, uses incorrect logic, or
does not follow the conventions of GPL enforcement, feel free to shoot
this idea down with utmost prejudice.
- Eric
next reply other threads:[~2013-05-18 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-18 8:21 Eric Appleman [this message]
[not found] <51973B45.7040209@gmail.com>
2013-05-20 15:13 ` Would like to form a pool of Linux copyright holders for faster GPL enforcement against Anthrax Kernels Bradley M. Kuhn
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=519739F9.7020508@gmail.com \
--to=erappleman@gmail.com \
--cc=linux-arm-kernel@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).