At the 2013 San Francisco Linux Collaboration talk I gave a talk 
as a followup on the discussions I initiated a while ago on lkml 
on the possibility of taking the Linux kernel's Developer Certificate
of Origin and streamlining it by making it a stand alone project for
other projects to benefit from it. This is a follow up to that talk.
W. Trevor King did some handy work by doing taking the Linux kernel's
DCO and making it a standalone project on github  and keeping its
history already. He's also made it project agnostic. To make a
standalone DCO project agnostic and useful for any type of project it
would help if any licensed project could use it. One question that we
had over this idea was whether or not the DCO is licensed under the
GPLv2 or not. Its arguable whether or not its copyrightable, perhaps
not but just the idea of contributions to it might make it so.
Although we could try to get a Creative Commons licensed DCO (and at
least for the standard body text, not the rest of SubmittingPatches
I'll go poke) King has made it possible for any licensed project to
use the DCO standalone project by making a Creative Commons licensed
file that simply refers to the public URL of the project.
As per discussions at LF collab it was acknowledged that the DCO could
indeed be a benefit to other projects but we'd need to ensure that the
body of the text is maintained as a very conservative document. I also
wanted to address volunteering a real life attorney to help with
reviews / maintenance so I volunteered Richard Fontana given Richard's
public work on copyleft-next and the copyleft-next mailing list
availability and his public work as an attorney for the community
there . Richard seems to have accepted.
What's next? Please join the copyleft-next mailing list if you are
interested in evolving the DCO and helping with streamlining this