From: "Bradley M. Kuhn" <bkuhn@sfconservancy.org>
To: <linux-kernel@vger.kernel.org>
Cc: Eric Appleman <erappleman@gmail.com>
Subject: Re: An example of prideful GPL violators who do their violating out in the open
Date: Thu, 02 Jan 2014 10:10:16 -0500 [thread overview]
Message-ID: <87ha9mqv1j.fsf@ebb.org> (raw)
In-Reply-To: <fa.amnYcw96YXPCJ5iHp+/ZK6pJJGk@ifi.uio.no>
Eric Appleman wrote a few days ago:
> https://plus.google.com/115556873499158641618/posts/KwG8uhU5DGk
> https://plus.google.com/102371604344319409727/posts/CSNGXqxzxf4
> https://plus.google.com/115556873499158641618/posts/ZegjCZ3FyDE
> I bet you've never seen such open hostility towards the GPL and its
> enforcement.
Actually, in my nearly 15 years of GPL enforcement, I've seen much worse
said about the GPL and its enforcement from much more eloquent and
knowledgeable folks. In the whole vast configuration of things,
Goodman's attacks on GPL are quite juvenile.
There are currently thousands of ongoing GPL violations impacting
millions of users. How many users are being impacted by Goodman's
violation? It can't be more than hundreds, and probably not more than
dozens. As a triage matter, my analysis of this hasn't changed since
the last time we discussed it, but I'm open-minded to reconsider if any
Linux copyright holders would like the GPL Compliance Project for Linux
Developers to do prioritize this violation. They know how to reach me.
--
Bradley M. Kuhn, Executive Director, Software Freedom Conservancy
(home of BusyBox, Samba, and the GPL Compliance Project for Linux Developers)
next parent reply other threads:[~2014-01-02 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.amnYcw96YXPCJ5iHp+/ZK6pJJGk@ifi.uio.no>
2014-01-02 15:10 ` Bradley M. Kuhn [this message]
2013-12-30 3:05 An example of prideful GPL violators who do their violating out in the open Eric Appleman
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=87ha9mqv1j.fsf@ebb.org \
--to=bkuhn@sfconservancy.org \
--cc=erappleman@gmail.com \
--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