From: "W. Trevor King" <wking@tremily.us>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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,
Alexey Dobriyan <adobriyan@gmail.com>,
Jim Meyering <meyering@redhat.com>,
Junio C Hamano <gitster@pobox.com>,
Miklos Vajna <mszeredi@suse.cz>,
Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>,
Ramkumar Ramachandra <artagnon@gmail.com>,
Willy Tarreau <w@1wt.eu>, Zac Storer <zac.3.14159@gmail.com>
Subject: Re: Streamlining Developer's Certificate of Origin, Signed-off-by tag
Date: Sat, 08 Dec 2012 11:22:57 -0500 [thread overview]
Message-ID: <20121208162257.GA27005@odin.tremily.us> (raw)
In-Reply-To: <20121124232202.GA29962@odin.tremily.us> <20121124142515.GA26479@odin.tremily.us> <20121121001043.7e1a68df@pyramind.ukuu.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1991 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.
For easy inclusion (preserving history), I've pulled out commits for
the DCO and related Signed-off-by documentation from Linux and Git
into a new repository [1].
On Sat, Nov 24, 2012 at 09:25:15AM -0500, W. Trevor King wrote:
> So. What license is the DCO distributed under and who holds
> copyright?
The Git project did some similar copying of the DCO into a new project
[2] and is (like the kernel) distributed under the GPLv2 exact. To be
consistent with this, I've also released the new signed-off-by
repository under the GPLv2 exact. If you're using a GPLv2 exact
project, you can merge the `signed-off-by` branch into your project
directly.
Because many projects that are not GPLv2 may still want to use the
DCO/s-o-b approach, I've included an example CONTRIBUTING file (and
CONTRIBUTING.md for GitHub) that are licensed under the very
permissive Creative Commons CC0 1.0 Universal. Merge the
`contributing` or `contributing-github` branch into your project and
edit as you see fit. For an example, see the GPLv{2,3} rss2email [3].
Cheers,
Trevor
[1]: https://github.com/wking/signed-off-by
https://github.com/wking/signed-off-by.git
git://github.com/wking/signed-off-by.git
[2]: https://github.com/gitster/git/commit/314082512403f7f6969cc6d5ded4a48c68a9962e
[3]: https://github.com/wking/rss2email/
--
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-12-08 17:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 20:59 Streamlining Developer's Certificate of Origin, Signed-off-by tag 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
2012-12-08 16:22 ` W. Trevor King [this message]
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=20121208162257.GA27005@odin.tremily.us \
--to=wking@tremily.us \
--cc=adobriyan@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arend@broadcom.com \
--cc=artagnon@gmail.com \
--cc=gitster@pobox.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=meyering@redhat.com \
--cc=mszeredi@suse.cz \
--cc=paolo.ciarrocchi@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
--cc=zac.3.14159@gmail.com \
/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