All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff.Haran@citrix.com (Jeff Haran)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel contributions from organisations and individual privacy
Date: Fri, 12 Jun 2015 23:29:51 +0000	[thread overview]
Message-ID: <4E5779AD88B2F040B8A7E83ECF544D1A603600@SJCPEX01CL03.citrite.net> (raw)
In-Reply-To: <557A35A0.5070608@surriel.com>

>-----Original Message-----
From: kernelnewbies-bounces@kernelnewbies.org [mailto:kernelnewbies-
>bounces at kernelnewbies.org] On Behalf Of Rik van Riel
>Sent: Thursday, June 11, 2015 6:28 PM
>To: Jeff Haran; kernelnewbies at kernelnewbies.org
>Subject: Re: Kernel contributions from organisations and individual privacy
>
>On 06/11/2015 08:13 PM, Jeff Haran wrote:
>>> On 06/11/2015 07:26 PM, Ruben Safir wrote:
>>>
>>>> Not at all.  You have a good point there are definitely legal
>>>> situations other than relicensing which are problematic.
>>>>
>>>> Lets say Apple decides that are going to take the Linux Kernel and
>>>> alter it extensively, in order for it to work with a new hardware
>>>> platform that they created. And lets say don't return the code base
>>>> to the
>>> public.
>>>> Now who is going to protect the license and sue them?  You have
>>>> literaly thousands of partiticpants who have standing now in this case.
>>>
>>> That means a thousand possible plaintiffs.
>>>
>>> s/Apple/VMware/ and you get this:
>>>
>>> http://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/
>>>
>>
>> I don't see in that web site the amount of damages they are asking for.
>Maybe I missed it.
>
>They are not asking for damages, but for license compliance.
>
>> Might get more money coming in for the plaintiff's lawyers if instead
>> of asking for contributions that yield a tee shirt, it was constructed
>> more like an investment, as in X% of total "contributions" gets the
>> investor X% of (damages - legal fees) should they win.
>
>I suspect that is not possible, since not every Linux kernel copyright holder will
>want to be part of a lawsuit (of any kind).
>
>The Conservancy is a non-profit. The defendants usually end up paying the
>legal costs (and sometimes a contribution for help with GPL compliance), but
>starting new actions is something that is funded by people like us, who care
>about preserving the GPL license.

All sounds very noble, but it would not seem to create much of a deterrence for violators.

What is the downside to a large company for violating GPL? They are likely to not get sued in the first place. If they are they can delay using court procedures until they've changed their code to not violate or GPL'ed it. Worst for them is paying legal fees and a contribution. I am guessing those aren't huge, not for a big company. Seems like unless there is some monetary sting like a piece of the proceeds on the sale of violating products, there is no deterrence and you guys will be in court for the rest of time chasing a never ending stream of new violators.

As for every copyright holder not wanting to be a part of the suit, I thought that was what class action suits were for.

Good luck to you but it sounds futile to me.

Jeff Haran

  reply	other threads:[~2015-06-12 23:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10  9:19 Kernel contributions from organisations and individual privacy Chris Packham
2015-06-11  4:58 ` Jason Ball
2015-06-11  5:10   ` Chris Packham
2015-06-11  5:19     ` Ruben Safir
2015-06-11 14:28       ` Greg KH
2015-06-11 14:41         ` Ruben Safir
2015-06-11 15:38           ` Greg KH
2015-06-11 16:39             ` Ruben Safir
2015-06-11 17:54               ` Greg KH
2015-06-11 17:57               ` Greg KH
2015-06-11 23:26                 ` Ruben Safir
2015-06-11 23:37                   ` Rik van Riel
2015-06-11 23:55                     ` Ruben Safir
2015-06-12  0:13                     ` Jeff Haran
2015-06-12  1:28                       ` Rik van Riel
2015-06-12 23:29                         ` Jeff Haran [this message]
2015-06-13 15:40                           ` Bjørn Mork
2015-06-13 19:08                             ` Ruben Safir
2015-06-15 23:08                             ` Jeff Haran
2015-06-15 23:55                               ` Rik van Riel
2015-06-16 16:23                                 ` Jeff Haran
2015-06-13 16:23                           ` Rik van Riel
2015-06-14 21:18                           ` Valdis.Kletnieks at vt.edu
     [not found]                             ` <B424B28F-AB7E-4972-95BB-FF91D85D0FED@gmail.com>
2015-06-14 23:29                               ` Valdis.Kletnieks at vt.edu
     [not found]                                 ` <557E0FF7.1000607@gmail.com>
2015-06-15  2:08                                   ` Valdis.Kletnieks at vt.edu
2015-06-12  0:52                   ` Greg KH
2015-06-12  3:31                   ` Valdis.Kletnieks at vt.edu
2015-06-12  4:39                     ` Ruben Safir
2015-06-12  7:18                       ` Valdis.Kletnieks at vt.edu
2015-06-11 13:13     ` Rik van Riel
2015-06-11 14:27   ` Greg KH
2015-06-11 14:25 ` Greg KH

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=4E5779AD88B2F040B8A7E83ECF544D1A603600@SJCPEX01CL03.citrite.net \
    --to=jeff.haran@citrix.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.