From: Chris Mason <clm@fb.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] GPL enforcement actions
Date: Tue, 7 Jul 2015 19:55:25 -0400 [thread overview]
Message-ID: <20150707235525.GA1522@ret.masoncoding.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F32AA4200@ORSMSX114.amr.corp.intel.com>
On Tue, Jul 07, 2015 at 10:15:24PM +0000, Luck, Tony wrote:
> > I'll bet the average core developer wants to hack on the kernel, and
> > share in the work that everyone else is doing. But I'll also bet the
> > conversation would be dominated by extremes, spiral down into
> > my-company-won't-let-me-say-xxyyzz, and then finally settle into
> > comparisons of US law with everyone else.
>
> A sizable fraction of commits come from people whose day job is
> to work on Linux. All my contributions to the Linux kernel are owned
> by my employer. Do companies with large aggregated contributions
> get a say in the GPL enforcement direction?
>
I think they've had a say all along, and our stability as a community
has benefited from it.
> I'm certainly not speaking for my employer here - but you might think
> that a company that makes a huge percentage of its profits from selling
> silicon chips would want the minimum possible barriers to people buying
> those chips to run s/w. That may, or may not, align with the opinions of
> people working for the company.
But what level of forced sharing actually makes the lowest barrier over
time? I'm happy to see us wander around with our wildly different
opinions about this. It makes for great debates, but it's not something
we can answer at KS.
But going back to David's original topic, there are some important
current events here. It's not a horrible idea to talk about them,
although Korea is pretty far to drag a lawyer for a single session.
-chris
next prev parent reply other threads:[~2015-07-07 23:55 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
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 [this message]
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=20150707235525.GA1522@ret.masoncoding.com \
--to=clm@fb.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tony.luck@intel.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