ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] GPL enforcement actions
Date: Tue, 07 Jul 2015 20:51:10 +0100	[thread overview]
Message-ID: <1436298670.3324.107.camel@infradead.org> (raw)
In-Reply-To: <20150707143447.6f345e91@gandalf.local.home>

On Tue, 2015-07-07 at 14:34 -0400, Steven Rostedt wrote:
> Would having a Lawyer be present also be required. That way we don't
> have everyone saying BS about what the law actually implies. Having a
> lawyer there as just someone to keep things real would be nice.

Lawyers will present whatever opinion they're paid to present. There is
no "right" answer until/unless it's seen in court. And then the ruling
only applies to specific circumstances. And is only binding in certain
jurisdictions, as you suggested. And until it's appealed.

I don't think a discussion about 'the true meaning of the GPL', or its
interpretation under specific legal systems, would be particularly
productive.

I think it would be good, though, to have a better understanding of
what people *want* the GPL to mean and what they *think* it means —
perhaps better phrased as "what they would pay a lawyer to argue".

The point is that we aren't attempting to reach a simple resolution
with a 'right answer'. There are parties with different desires — from
demanding strict compliance with the *maximum* they can argue for the
GPL to mean, to basically wanting to act as if it's a BSD licence, in
order to avoid scaring commercial users away and feeding FUD stories
like this one¹.

It would be useful to have an idea of where the average core developer
falls within that spectrum — that was the first specific thing I was
hoping would come from the proposed session.

The other specific goal (and perhaps the more important one) was to
have a coherent report about the enforcement actions and behind-the
-scenes negotiations w.r.t compliance that there is so much
misinformation and politicking about.

To that end, we should probably invite Bradley Kuhn or Karen Sandler
from SF Conservancy to talk about their efforts. And someone from the
LF TAB will presumably also be there to discuss the compliance
viewpoint from the LF side.

-- 
dwmw2
¹ http://sdtimes.com/from-the-editors-when-did-open-source-software-get-so-scary/

  reply	other threads:[~2015-07-07 19:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-04  8:06 David Woodhouse
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 [this message]
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=1436298670.3324.107.camel@infradead.org \
    --to=dwmw2@infradead.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=rostedt@goodmis.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