On 17. 01. 19 12:59, Randy Barlow wrote:
On Thu, 2019-01-17 at 11:13 +0100, Miro Hrončok wrote:
Why do Fedora upstreams enforce this?
I enforce the DCO in Bodhi. I started doing it after attended a talk by Richard Fontana where he suggested it as a way to be explicit about the license of contributions (i.e., not just the license of the project). My memory is now a bit hazy, but I think there was some discussion about how many projects work under the assumption that the license of contributions is equal to the license of the project (sometimes stated as "license in, license out", but that most do not make this explicit. The DCO explicitly states that the contribution itself is granted to the project under the same license that the project uses.
I'd be very interested to know how adding some random line to a commit message grants an explicit license according to something that is not even linked from the commit message :(
CCing legal.
On Thu, 2019-01-17 at 13:04 +0100, Miro Hrončok wrote:
I'd be very interested to know how adding some random line to a commit message grants an explicit license according to something that is not even linked from the commit message :(
I've actually wondered this myself, and agree that it does seem odd. It's not like the message says "I agree to the DCO, signed xyz."
For Bodhi, I decided to document what the sign off means in the contribution guide:
https://bodhi.fedoraproject.org/docs/developer/index.html#contribution-guide...
Of course, that doesn't mean that all contributors read the contribution guide, but that's the best I could think to do for now.
On Thu, Jan 17, 2019 at 7:54 AM Randy Barlow bowlofeggs@fedoraproject.org wrote:
On Thu, 2019-01-17 at 13:04 +0100, Miro Hrončok wrote:
I'd be very interested to know how adding some random line to a commit message grants an explicit license according to something that is not even linked from the commit message :(
I've actually wondered this myself, and agree that it does seem odd. It's not like the message says "I agree to the DCO, signed xyz."
For Bodhi, I decided to document what the sign off means in the contribution guide:
https://bodhi.fedoraproject.org/docs/developer/index.html#contribution-guide...
Of course, that doesn't mean that all contributors read the contribution guide, but that's the best I could think to do for now.
Projects using the DCO should normally have a copy of the DCO in the source repository in some place where a contributor can reasonably be expected to see it. A couple of examples: https://github.com/ceph/ceph/blob/master/SubmittingPatches.rst (linked to from https://github.com/ceph/ceph/blob/master/CONTRIBUTING.rst ) https://github.com/ansible/awx/blob/devel/DCO_1_1.md
-
Miro Hrončok -
Randy Barlow -
Richard Fontana