All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel contributions from organisations and individual privacy
Date: Thu, 11 Jun 2015 10:54:36 -0700	[thread overview]
Message-ID: <20150611175436.GE22639@kroah.com> (raw)
In-Reply-To: <5579B9D3.9030208@mrbrklyn.com>

On Thu, Jun 11, 2015 at 12:39:47PM -0400, Ruben Safir wrote:
> On 06/11/2015 11:38 AM, Greg KH wrote:
> > On Thu, Jun 11, 2015 at 10:41:57AM -0400, Ruben Safir wrote:
> >> On 06/11/2015 10:28 AM, Greg KH wrote:
> >>>> If the copyright is owned by the company then ONLY the company can push
> >>>>> it up stream and assign copyright to the Linux Foundation.
> >>> No one assigns kernel copyright to the Linux Foundation unless you have
> >>> entered into some odd business agreement with that legal entity.  And
> >>> that is quite rare to do so and takes lots of lawyers and time.
> >>
> >>
> >> It doesn't take a lot of lawyers anymore than a license would.  I
> >> thought that the Foundation requests this routinely in order so that it
> >> has standing in court if a lawsuit should happen.
> > 
> > No, it never has done this, where are you getting this crazy idea?
> 
> 
> This idea is not crazy.  During the SCO battle this problem got tossed
> about quite a bit and I thought that at that time the Linux Foundation
> and Mad Dog set up a Copyright Clearing House for the Kernel.  Your
> saying that this never happened, so maybe I'm wrong.

You are wrong.

Also, the Linux Foundation didn't even exist at the time of the start of
the SCO "issues", so I don't know who you were talking to.

> The problem is two fold.  First the Foundation and Linus need standing
> in court cases where violations of the GPL2 were involved...if there was
> such need.  That is best established with assignment of the copyright,
> bit done through a contributor license agreement.

That is not true at all, and is not a best practice that I would
encourage any project to take.  In fact, I don't contribute to any such
project, and strongly recommend that no one else would do so either.

> I never claimed, BTW, that this was forced on everyone.  But I thought
> it was encouraged since the SCO battle.

Nope, again, didn't happen, isn't an issue, you own your own copyright
of any code you contribute to the kernel, end of story.

thanks,

greg k-h

  reply	other threads:[~2015-06-11 17:54 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 [this message]
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
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=20150611175436.GE22639@kroah.com \
    --to=greg@kroah.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.