mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Denis 'GNUtoo' Carikli" <GNUtoo@no-log.org>
To: Eric Appleman <erappleman@gmail.com>
Cc: legal@lists.gpl-violations.org, linux-kernel@vger.kernel.org
Subject: Re: Would like to form a pool of Linux copyright holders for faster GPL enforcement against Anthrax Kernels
Date: Wed, 22 May 2013 17:59:08 +0200	[thread overview]
Message-ID: <20130522175908.0551ae88@m4a785t-m.lan> (raw)
In-Reply-To: <51972CAF.3060802@gmail.com>

On Sat, 18 May 2013 03:24:31 -0400
Eric Appleman <erappleman@gmail.com> wrote:

> 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.
yes, unfortunately I've only non-crucial code in mainline:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?qt=author&q=Denis+%27GNUtoo%27+Carikli
The drivers and hardware touched by my code are obsolete and will
probably not be used in newer products.

I've also some code not mentioned in the link above that made it into
mainline that I did for work. Since I don't own the copyright of it (my
employer does), it's not covered by this agreement.

> 
> Last I checked, I have 1 long-time poster of this list on board.
> Would anyone else like to join?
yes, as long as it doesn't require spending too much time on it.

> Ideally I'd like to get the LKML
> (which I have CC'd) 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
ok
> * Formally requesting removal of critical copyrighted code that Linux 
> cannot function without
I've no crucial code in mainline unfortunately.
> * Informing interested parties with respect to refusals of the above
ok
> 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, uses incorrect logic, or does not follow the 
> conventions of GPL enforcement, feel free to shoot this idea down
> with utmost prejudice.
Seem good.

Denis.

      parent reply	other threads:[~2013-05-22 17:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-18  7:24 Eric Appleman
2013-05-18  8:28 ` Eric Appleman
2013-05-18 18:27 ` luke.leighton
     [not found]   ` <1368918189923.dd7325ed@Nodemailer>
2013-05-19 10:39     ` luke.leighton
2013-05-19 11:04       ` Ralph Corderoy
2013-05-19 12:24         ` luke.leighton
2013-05-19 18:01           ` Thomas Charron
2013-05-19 11:19       ` Jonas Gorski
2013-05-19 12:34         ` luke.leighton
2013-05-19 13:28           ` Jonas Gorski
2013-05-19 13:45             ` Theodore Ts'o
2013-05-19 18:06           ` Thomas Charron
2013-05-19 17:55       ` Thomas Charron
     [not found]   ` <ce644e6e12d68aaabed7403b5f21c124@imap.plus.net>
2013-05-19 10:57     ` luke.leighton
2013-05-19 13:53       ` Phil Turmel
2013-05-20 10:24       ` Ian Stirling
2013-05-20 11:33         ` Theodore Ts'o
2013-05-22 16:13       ` Denis 'GNUtoo' Carikli
2013-05-22 17:56         ` Theodore Ts'o
2013-05-21 10:11   ` Rob Landley
2013-05-22 15:45   ` Denis 'GNUtoo' Carikli
2013-05-22 15:59 ` Denis 'GNUtoo' Carikli [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=20130522175908.0551ae88@m4a785t-m.lan \
    --to=gnutoo@no-log.org \
    --cc=erappleman@gmail.com \
    --cc=legal@lists.gpl-violations.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®