From: "W. Trevor King" <wking@tremily.us>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
Arend van Spriel <arend@broadcom.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: Streamlining Developer's Certificate of Origin, Signed-off-by tag
Date: Sat, 24 Nov 2012 09:25:15 -0500 [thread overview]
Message-ID: <20121124142515.GA26479@odin.tremily.us> (raw)
In-Reply-To: <20121121001043.7e1a68df@pyramind.ukuu.org.uk>
[-- Attachment #1: Type: text/plain, Size: 2171 bytes --]
On Wed, Nov 21, 2012 at 12:10:43AM +0000, Alan Cox wrote:
> > Not just a separate document but project / github / whatever given
> > that other projects are referring to it now, and we stand to gain more
> > in the community by streamlining it more and making it ubiquitous.
>
> Cutting and pasting it somewhere works (subject to whatever licensing
> it may have itself), as does having a list and a location for a copy, but
> you still want it in the tree proper.
I'm transitioning a project to the DCO-1.1 and trying to get its
licensing straightened out. The DCO-1.0 [1] and DCO-1.1 [2] commits
were both by Linus, but lacked SOB lines in the commit. The initial
proposal was also by Linus [3] (and this initial DCO version is what
was committed in [1]). However, the OSDL (where Linus was working at
the time) seems to claim copyright for itself and claims
CC-BY-SA-2.5-generic [4]. Strangely, the DCO-1.1 text listed on the
archived OSDL page does not match the text of the DCO-1.1 text in the
kernel tree (the differences look minor to me, but I'm not a laywer).
So. What license is the DCO distributed under and who holds
copyright?
Cheers,
Trevor
[1]: From: Linus Torvalds
Subject: Start documenting the sign-off procedure in SubmittingPatches
Date: 2004-06-01 19:13:52 GMT
Gmane: http://permalink.gmane.org/gmane.linux.kernel.commits.head/33254
ChangeSet 1.1726.1.148, 2004/06/01 12:13:52-07:00, torvalds…
[2]: commit cbd83da82b15292337ff2b71e619c9a3a95f6d80
Author: Linus Torvalds <torvalds@ppc970.osdl.org>
Date: Mon Jun 13 17:51:55 2005 -0700
Update DCO ("signoff") rules to 1.1
[3]: From: Linus Torvalds <torvalds <at> osdl.org>
Subject: [RFD] Explicitly documenting patch submission
Date: 2004-05-23 06:46:29 GMT
Gmane: http://article.gmane.org/gmane.linux.kernel/205867
[4]: http://web.archive.org/web/20070306195036/http://osdlab.org/newsroom/press_releases/2004/2004_05_24_dco.html
--
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-24 15:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 20:59 Luis R. Rodriguez
2012-11-20 21:16 ` Alan Cox
2012-11-20 22:08 ` Arend van Spriel
2012-11-20 22:21 ` Luis R. Rodriguez
2012-11-21 0:10 ` Alan Cox
2012-11-21 1:13 ` Luis R. Rodriguez
2012-11-21 9:40 ` Jiri Slaby
2012-11-21 14:54 ` Alan Cox
2012-11-24 14:25 ` W. Trevor King [this message]
2012-12-08 16:22 ` W. Trevor King
2013-02-26 21:37 ` Luis R. Rodriguez
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=20121124142515.GA26479@odin.tremily.us \
--to=wking@tremily.us \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arend@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®