On Tue, May 20, 2025 at 10:06 AM Ghanshyam Maan <gmaan@ghanshyammann.com> wrote:

---- On Mon, 19 May 2025 23:54:48 -0700 Thierry Carrez <thierry@openstack.org> wrote ---

...

Hi,

It's worth noting that back in 2014, the TC already voted on a resolution asking to move all CLAs to DCO:

"The OpenStack Technical Committee, representing the developer community, requests that the Board of Directors consider implementing the Developer Certificate of Origin (DCO) as the Contributor License Agreement (CLA) for the OpenStack project. [...]"

https://governance.openstack.org/tc/resolutions/20140909-cla.html

So this is more of a check to see if that resolution still holds :)

++, We have not overridden this resolution of not using DCO, but as this is too old a resolution, maybe we can propose/confirm the same with a new resolution.

Pursuant to today's TC meeting [1], I've raised a resolution here: https://review.opendev.org/c/openstack/governance/+/950463 Please feel free to review. The main concern expressed at today's meeting was about the implications of a quick change. Even if we always wanted this, the timeline to change everything is short (June 1st is 10 days from now). Many companies have formal policies regarding open-source contributions. After we inform them, they may need to re-engage their legal teams to discuss the effect of this change and adapt. It might end up delaying contributions. While the technical implementation/enforcement of DCO in Gerrit seems straightforward, the "human component" of communication and policy adjustment seems complex.

-gmaan

...

Thierry Carrez (ttx)

Jonathan Bryce wrote:

...

Hi everyone,

I wanted to flag a recent message on the Foundation mailing list about the possibility to move OpenInfra projects from using the Contributor License Agreement (CLA) to the Developer Certificate of Origin (DCO) [1].

This change would be part of the broader transition into the Linux Foundation and could take effect starting June 1, 2025. It’s something the Board has supported for newer projects, and now existing projects like OpenStack have the opportunity to make the switch as well.

I’m happy to join the TC meeting this week to discuss.

Thanks,

Jonathan

1. https://lists.openinfra.org/archives/list/foundation@lists.openinfra.org/thr...

On 20/05/2025 21:58, Goutham Pacha Ravi wrote:

On Tue, May 20, 2025 at 1:58 PM Goutham Pacha Ravi <gouthampravi@gmail.com> wrote:

...

On Tue, May 20, 2025 at 10:06 AM Ghanshyam Maan <gmaan@ghanshyammann.com> wrote:

...

---- On Mon, 19 May 2025 23:54:48 -0700 Thierry Carrez <thierry@openstack.org> wrote ---

...

Hi,

It's worth noting that back in 2014, the TC already voted on a resolution asking to move all CLAs to DCO:

"The OpenStack Technical Committee, representing the developer community, requests that the Board of Directors consider implementing the Developer Certificate of Origin (DCO) as the Contributor License Agreement (CLA) for the OpenStack project. [...]"

https://governance.openstack.org/tc/resolutions/20140909-cla.html

So this is more of a check to see if that resolution still holds :)

++, We have not overridden this resolution of not using DCO, but as this is too old a resolution, maybe we can propose/confirm the same with a new resolution. Pursuant to today's TC meeting [1], I've raised a resolution here: https://review.opendev.org/c/openstack/governance/+/950463 Please feel free to review.

The main concern expressed at today's meeting was about the implications of a quick change. Even if we always wanted this, the timeline to change everything is short (June 1st is 10 days from now). Many companies have formal policies regarding open-source contributions. After we inform them, they may need to re-engage their legal teams to discuss the effect of this change and adapt. It might end up delaying contributions.

10 days seams unlikely a more realistic goal is probably by the end of this cycle. i.e. have it take effect formally form the start of 2026.1 development cycle. the infra to support that and communication can happen on a shorter timeline but a hard switch over by june 1st seam hard.

...

While the technical implementation/enforcement of DCO in Gerrit seems straightforward, the "human component" of communication and policy adjustment seems complex.

correct me if im wrong but the main change we need to enforce that all commit would have signed-off-by going forward to signify that it was commit under the DCO. if we enforce it at the gerrit level then that would also require the bot proposed patches to be updated. That would also mean updating all open gerrit patches... which we can do but that will take time and muscel memory is also a factor.

(apologies hit send too soon): [1] https://meetings.opendev.org/meetings/tc/2025/tc.2025-05-20-17.00.log.html

...

...

-gmaan

...

Thierry Carrez (ttx)

Jonathan Bryce wrote:

...

Hi everyone,

I wanted to flag a recent message on the Foundation mailing list about the possibility to move OpenInfra projects from using the Contributor License Agreement (CLA) to the Developer Certificate of Origin (DCO) [1].

This change would be part of the broader transition into the Linux Foundation and could take effect starting June 1, 2025. It’s something the Board has supported for newer projects, and now existing projects like OpenStack have the opportunity to make the switch as well.

I’m happy to join the TC meeting this week to discuss.

Thanks,

Jonathan

1. https://lists.openinfra.org/archives/list/foundation@lists.openinfra.org/thr...