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:57:00 -0700	[thread overview]
Message-ID: <20150611175700.GF22639@kroah.com> (raw)
In-Reply-To: <5579B9D3.9030208@mrbrklyn.com>

On Thu, Jun 11, 2015 at 12:39:47PM -0400, Ruben Safir wrote:
> > The only thing you have to agree with when contributing Linux kernel
> > code is the DCO, which can be found in the file
> > Documentation/SubmittingPatches, or here online:
> > 	http://developercertificate.org/
> > 
> 
> I didn't know that and looking at it, that is pretty flimsy.

Not at all, in fact, it's very strong.  A number of other projects also
use this same document (SAMBA, Docker, etc.), so it is well known and
proven to work.

> It is a good thing that up until know this hasn't bit them in the ass
> so far.  I might be all that is possible though because a CLA, to be
> really blanket, would require one having to go back to every
> contribution to date.

That's only if you wanted to do something crazy like relicense the work.
And even then, a CLA doesn't help you out, see all of the projects that
have undertaken this task and what they have done to enable it.  A CLA
doesn't do much there.

greg k-h

  parent reply	other threads:[~2015-06-11 17:57 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 [this message]
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=20150611175700.GF22639@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.