Proposal: Use and Require CLA for QA Devel Project Contributions
Dan Callaghan
dcallagh at redhat.com
Tue May 20 22:16:15 UTC 2014
Just some food for thought... You might consider adopting a "Developer
Certificate of Origin" (with agreement indicated by a Signed-off-by
footer in git commit messages) like the Linux kernel, rather than a CLA.
A good summary here:
http://lwn.net/Articles/592503/
The wording of the Linux DCO doesn't give permission to re-license but
if new code is contributed under GPLv2+ it seems like that should give
you enough leeway to deal with the GPLv3-only stuff.
It also has the advantage of avoiding the dread "CLA" phrase which in
many people's minds conjures up unpleasant images of copyright
assignment and proprietary re-licensing.
--
Dan Callaghan <dcallagh at redhat.com>
Software Engineer, Hosted & Shared Services
Red Hat, Inc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/qa-devel/attachments/20140521/bed03afb/attachment.sig>
More information about the qa-devel
mailing list