From mboxrd@z Thu Jan 1 00:00:00 1970 From: greg@kroah.com (Greg KH) Date: Thu, 11 Jun 2015 10:57:00 -0700 Subject: Kernel contributions from organisations and individual privacy In-Reply-To: <5579B9D3.9030208@mrbrklyn.com> References: <55791A7C.1030904@mrbrklyn.com> <20150611142829.GC17984@kroah.com> <55799E35.5080608@mrbrklyn.com> <20150611153813.GA5058@kroah.com> <5579B9D3.9030208@mrbrklyn.com> Message-ID: <20150611175700.GF22639@kroah.com> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org 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