From: David Woodhouse <dwmw2@infradead.org>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] [CORE TOPIC] GPL enforcement actions
Date: Sat, 04 Jul 2015 09:06:01 +0100 [thread overview]
Message-ID: <1435997161.3324.33.camel@infradead.org> (raw)
I'm slightly loath to bring this up but I think it does need doing...
There are various people involved with GPL enforcement actions for the
kernel, and there seems to be a lot of misinformation about it all.
Some parties are portrayed as acting excessively and inappropriately —
and with dubious motives — to enforce the GPL; others as being rabidly
*against* enforcement and effectively wanting a BSD-licensed free-for
-all because that supports their corporate interests.
None of these portrayals are entirely accurate, I'm sure, and the
histrionics don't really do anyone any good.
I'm sure we won't reach a universal consensus, but it would be useful
to get the interested parties together and have a coherent discussion
about it, so that everyone can have a proper understanding of the fact,
and also a reasonable idea of the 'feeling in the room' regarding if,
when and how we require compliance with the GPL.
--
dwmw2
next reply other threads:[~2015-07-04 8:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-04 8:06 David Woodhouse [this message]
2015-07-04 10:18 ` David Howells
2015-07-04 16:49 ` David Woodhouse
2015-07-07 18:34 ` Steven Rostedt
2015-07-07 19:51 ` David Woodhouse
2015-07-07 20:00 ` Greg KH
2015-07-07 20:18 ` David Woodhouse
2015-07-07 22:11 ` John W. Linville
2015-07-08 15:41 ` Tim Bird
2015-07-08 21:25 ` Greg KH
2015-07-08 22:55 ` Tim Bird
2015-07-07 20:33 ` Chris Mason
2015-07-07 22:15 ` Luck, Tony
2015-07-07 23:55 ` Chris Mason
2015-07-07 21:06 ` Guenter Roeck
2015-07-31 18:45 ` Christoph Lameter
2015-07-31 19:06 ` James Bottomley
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=1435997161.3324.33.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=ksummit-discuss@lists.linuxfoundation.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