All of lore.kernel.org
 help / color / mirror / Atom feed
From: ruben@mrbrklyn.com (Ruben Safir)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel contributions from organisations and individual privacy
Date: Thu, 11 Jun 2015 19:26:23 -0400	[thread overview]
Message-ID: <20150611232623.GA2026@www.mrbrklyn.com> (raw)
In-Reply-To: <20150611175700.GF22639@kroah.com>

On Thu, Jun 11, 2015 at 10:57:00AM -0700, Greg KH wrote:
> 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.
> 

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.  Apple can just
blow there nose at you if they are willing to put up with the bad publicity.

anyway...

http://www.h-online.com/open/features/Copyright-assignment-Once-bitten-twice-shy-1049631.html

and I'm finished with this commentary.

Broadly I agree with you and the CLA discussion is a side track.

> greg k-h
> 
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

-- 
So many immigrant groups have swept through our town
that Brooklyn, like Atlantis, reaches mythological
proportions in the mind of the world - RI Safir 1998
http://www.mrbrklyn.com 

DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002
http://www.nylxs.com - Leadership Development in Free Software
http://www2.mrbrklyn.com/resources - Unpublished Archive 
http://www.coinhangout.com - coins!
http://www.brooklyn-living.com 

Being so tracked is for FARM ANIMALS and and extermination camps, 
but incompatible with living as a free human being. -RI Safir 2013

  reply	other threads:[~2015-06-11 23:26 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 [this message]
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=20150611232623.GA2026@www.mrbrklyn.com \
    --to=ruben@mrbrklyn.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.