[ros-users] [Discourse.ros.org] [Next Generation ROS] Starting to enforce Developer Certificate of Origin (DCO) for (some) ROS 2 repos

gavanderhoorn via Discourse.ros.org ros.discourse at gmail.com
Fri Jan 11 21:03:29 UTC 2019

[quote="dirk-thomas, post:1, topic:7420"]

With the Crystal release being out of the door we will follow up on the previously mentioned goal to enforcement a [Developer Certificate of Origin (DCO) ](https://developercertificate.org/) on contributions to core ROS 2 repositories [[1 ](https://discourse.ros.org/t/introducing-the-ros-2-technical-steering-committee/6132)].


In the linked post @gerkey doesn't give a rationale, it contains merely a statement of intent:

>  Were also working on updates to developer policies, such as enforcement of a [Developer Certificate of Origin (DCO) ](https://developercertificate.org/) on contributions to core ROS 2 repositories.

In https://discourse.ros.org/t/ros-2-tsc-meeting-minutes-july-24th-2018/6156 it's also only stated that DCO will be required. https://discourse.ros.org/t/ros-2-tsc-meeting-minutes-september-6th-2018/6157 states "Explain rationale, say that well take comments now and at ROSCon".

It's probably obvious, but could you perhaps provide some insight into the reasoning behind this decision?

I've probably missed it, so if there was any discussion at ROSCon about enforcing DCOs, my apologies.


[Visit Topic](https://discourse.ros.org/t/starting-to-enforce-developer-certificate-of-origin-dco-for-some-ros-2-repos/7420/2) or reply to this email to respond.

More information about the ros-users mailing list