ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Tim Bird <tim.bird@sonymobile.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] GPL enforcement actions
Date: Wed, 8 Jul 2015 14:25:12 -0700	[thread overview]
Message-ID: <20150708212512.GA31140@kroah.com> (raw)
In-Reply-To: <559D44AF.9090406@sonymobile.com>

On Wed, Jul 08, 2015 at 08:41:35AM -0700, Tim Bird wrote:
> 
> 
> On 07/07/2015 01:18 PM, David Woodhouse wrote:
> > On Tue, 2015-07-07 at 13:00 -0700, Greg KH wrote:
> >> As those "efforts" are being driven by the developers of the kernel, I
> >> think that the developers involved would be the best to present this,
> >> not the SF Conservancy people.  As you point out, the SFLC is just the
> >> lawyers being hired by the developers to do what they want them to do :)
> > 
> > A lot of those developers will be in the room too, of course.
> > 
> > But the "efforts" are being driven *by* Conservancy on *behalf* of
> > those developers who have asked Conservancy to do so. And I suspect
> > someone from Conservancy is better placed to give up-to-date
> > information about what's actually happening "on the ground".
> > 
> > The point is to get people in the room and have a direct discussion
> > without hearsay or misinformation — and doing that *without* someone
> > from Conservancy doesn't really make much sense.
> 
> My experience with this is that you'll get one side (and perspective)
> of the compliance enforcement story, only.  Companies involved in
> compliance "improvement" exercises simply will not comment on them, so
> it's not easy to tell if the remedies being requested are understood
> by all parties or not, and whether I'd agree with them.

s/will not/usually can not/g

I'm worried that since a lot of people can't talk about this, for
various reasons, that the usefulness of it might not be all that
helpful.

> From my standpoint it would be useful to hear the Conservancy's stance
> on a few issues.

What specific issues are you curious about that you think would be
good to discuss / hear about?

thanks,

greg k-h

  reply	other threads:[~2015-07-08 21:25 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
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 [this message]
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=20150708212512.GA31140@kroah.com \
    --to=greg@kroah.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=tim.bird@sonymobile.com \
    /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