Linus, this is not limited to us, so I am bothering you; sorry about that. My instinct tells me that some competent lawyers at linux-foundation helped you with the wording of DCO, and we amateurs shouldn't be mucking with the text like this patch does at all, but just in case you might find it interesting...
Richard Hansen <rhan...@bbn.com> writes: > The "Developer's Certificate of Origin" refers to "the open source > license indicated in the file", but there is no such indication in > most files in the Git repository. > > Update the text to indicate that the license in COPYING should be > assumed if a file doesn't excplicitly indicate which license applies > to the file. > > The phrase "accompanies the file" was chosen to support different > default licenses in different subdirectories (e.g., 2-clause BSD for > vcs-svn/*, LGPL2.1+ for xdiff/*). > > Signed-off-by: Richard Hansen <rhan...@bbn.com> > --- > I'm bringing this up because, to this layman's eyes, it seems like a > potentially troublesome oversight. IIUC, one of the purposes of the > Developer's Certificate of Origin is to make it easy for developers to > declare which license covers a contribution. Requiring a license > declaration protects the project and its users from copyright > litigation. > > What happens if the file(s) being modified do not indicate which > license applies to the file? Is there no license? Does it default to > the main project license in COPYING? This lack of clarity makes me a > bit nervous (law is already too nondeterministic for my liking), so > I'd like to see a change that makes it explicit. > > Notes: > * I am not a lawyer. (Maybe a lawyer should be consulted?) > * This change might not be necessary. > * This change might be wrong. > * I hope I'm not just wasting everyone's time by bringing this up. > > Documentation/SubmittingPatches | 9 ++++++--- > 1 file changed, 6 insertions(+), 3 deletions(-) > > diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches > index 7055576..c5ff744 100644 > --- a/Documentation/SubmittingPatches > +++ b/Documentation/SubmittingPatches > @@ -227,13 +227,15 @@ the patch, which certifies that you wrote it or > otherwise have > the right to pass it on as a open-source patch. The rules are > pretty simple: if you can certify the below: > > - Developer's Certificate of Origin 1.1 > + Developer's Certificate of Origin 1.2 > > By making a contribution to this project, I certify that: > > (a) The contribution was created in whole or in part by me and I > have the right to submit it under the open source license > - indicated in the file; or > + indicated in the file (or, if no license is indicated in > + the file, the license in COPYING that accompanies the > + file); or > > (b) The contribution is based upon previous work that, to the best > of my knowledge, is covered under an appropriate open source > @@ -241,7 +243,8 @@ pretty simple: if you can certify the below: > work with modifications, whether created in whole or in part > by me, under the same open source license (unless I am > permitted to submit under a different license), as indicated > - in the file; or > + in the file (or, if no license is indicated in the file, > + the license in COPYING that accompanies the file); or > > (c) The contribution was provided directly to me by some other > person who certified (a), (b) or (c) and I have not modified -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
