On Tue, May 20, 2025 at 5:52 PM Sean Mooney <smooney@redhat.com> wrote:
>
>
> 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.

+1
>
> 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.

We discussed this some more on the #openstack-tc channel [2] and on
the gerrit change itself. The new proposal is to require the DCO from
July 1st 2025. It isn't set in stone, Jonathan will follow up with the
OpenInfra Foundation legal team.

>
> >>
> >> 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.

this is correct. To follow DCO, all commits will require a
"Signed-off-by" comment. This is required from the original committer
as well as anyone that modifies a Gerrit change by submitting new
commits [3]


>
> 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.
>

great point on bot proposed changes. Note that we'll not _need_ to
update anything on gerrit to add the "Signed-off-by" line. This needs
to be done only on new commits. You could add a new commit to an
existing change by amending a previous commit (this includes rebases)
- when we begin enforcing DCO compliance, your new commit will need
"Signed-off-by" in the commit message.

Unfortunately, this means that, on the Web UI, you cannot hit a button
to "Rebase" a change that doesn't have "Signed-off-by" in the commit
message. If you're inclined to use the UI, you'll need to first edit
the commit message, and add a "Signed-off-by" with your name and
email, and then hit the "Rebase" button. Hopefully this pain is short
term.

Jeremy Stanley helped set up an experiment on DCO enforcement on the
opendev/sandbox repository on https://review.opendev.org. If you'd
like to play around, please do so before EOD on Friday, May 23rd 2025.
As a maintainer, I found this super useful to predict the contributor
experience/pain points.

On enforcement, if you commit without "Signed-off-by", you should see
an error message similar to:

"Could not perform action: not Signed-off-by author/committer/uploader
in message footer" on the UI or
 ! [remote rejected] HEAD -> refs/for/master (commit: not
Signed-off-by author/committer/uploader in message footer) in the
git-review CLI

[2] https://meetings.opendev.org/irclogs/%23openstack-tc/%23openstack-tc.2025-05-21.log.html#openstack-tc.2025-05-21.log.html#t2025-05-21T16:01:20

>
> > (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/thread/PXMTX67TRL2B4ONICTT2E2XZLG4J4LAL/
> >>>   >
> >>>   >
> >>>   >
> >>>   >
> >>>
>