# Starting to enforce Developer Certificate of Origin (DCO) for (some) ROS 2 repos

**URL:** <https://discourse.openrobotics.org/t/starting-to-enforce-developer-certificate-of-origin-dco-for-some-ros-2-repos/7420>\
**Category:** ROS General\
**Created:** [January 11, 2019, 8:07pm UTC](https://discourse.openrobotics.org/t/starting-to-enforce-developer-certificate-of-origin-dco-for-some-ros-2-repos/7420 "2019-01-11T20:07:59Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![dirk-thomas](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/dirk-thomas/32/4328_2.png) [@dirk-thomas](https://discourse.openrobotics.org/u/dirk-thomas)\
**Post date:** [March 20, 2019, 4:12pm UTC](https://discourse.openrobotics.org/t/starting-to-enforce-developer-certificate-of-origin-dco-for-some-ros-2-repos/7420/7 "2019-03-20T16:12:14Z")

</div>

In the mean time we have enabled the DCO check to a number of repositories (see [add section about DCO to CONTRIBUTING.md by dirk-thomas · Pull Request #210 · ros2/ros2cli · GitHub](https://github.com/ros2/ros2cli/pull/210#issuecomment-474900128) for the complete list) and added a note about the DCO to the `CONTRIBUTING.md` file to each of these repositories.

Happy signing off ✔

---

_[View the full topic](https://discourse.openrobotics.org/t/starting-to-enforce-developer-certificate-of-origin-dco-for-some-ros-2-repos/7420)._