Moving from CLA to DCO for OpenInfra Contributions
Hi StarlingX community, I'm reaching out 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 the end of June. It’s something the Board has supported for newer projects, and now existing projects like StarlingX have the opportunity to make the switch as well. Please let me know what questions or concerns you have regarding this change. Thanks and Best Regards, Ildikó [1] https://lists.openinfra.org/archives/list/foundation@lists.openinfra.org/thr... ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation
Hi StarlingX community, I'm reaching out with a quick update. As you might've already learned from the resources my previous email pointed to, the Contributor License Agreement (CLA) will soon not be applicable to OpenInfra projects. On the last TSC & Community call the TSC and community members briefly discussed next steps and were in an agreement to implement the DCO process as a successor. Next steps will include: - Updating settings in Gerrit to stop enforcing the CLA - Ildiko + Jeremy - Document the new DCO process, or keep relying on the OpenStack community's guidelines as they become available - Updating any documentation (Contributor Guides, READMEs, etc) in StarlingX that mention the CLA to refer to the new DCO process - StarlingX community - Implement DCO enforcement in Gerrit - Updating config options that are currently used when creating new repos Please let me know if you have any questions. Thanks and Best Regards, Ildikó ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation
On May 27, 2025, at 10:13, Ildiko Vancsa <ildiko@openinfra.dev> wrote:
Hi StarlingX community,
I'm reaching out 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 the end of June. It’s something the Board has supported for newer projects, and now existing projects like StarlingX have the opportunity to make the switch as well.
Please let me know what questions or concerns you have regarding this change.
Thanks and Best Regards, Ildikó
[1] https://lists.openinfra.org/archives/list/foundation@lists.openinfra.org/thr...
———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
Thanks for the update, this all sounds reasonable to me. Chris On 5/30/2025 5:07 PM, Ildiko Vancsa wrote:
CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi StarlingX community,
I'm reaching out with a quick update.
As you might've already learned from the resources my previous email pointed to, the Contributor License Agreement (CLA) will soon not be applicable to OpenInfra projects. On the last TSC & Community call the TSC and community members briefly discussed next steps and were in an agreement to implement the DCO process as a successor.
Next steps will include: - Updating settings in Gerrit to stop enforcing the CLA - Ildiko + Jeremy - Document the new DCO process, or keep relying on the OpenStack community's guidelines as they become available - Updating any documentation (Contributor Guides, READMEs, etc) in StarlingX that mention the CLA to refer to the new DCO process - StarlingX community - Implement DCO enforcement in Gerrit - Updating config options that are currently used when creating new repos
Please let me know if you have any questions.
Thanks and Best Regards, Ildikó
———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
On May 27, 2025, at 10:13, Ildiko Vancsa<ildiko@openinfra.dev> wrote:
Hi StarlingX community,
I'm reaching out 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 the end of June. It’s something the Board has supported for newer projects, and now existing projects like StarlingX have the opportunity to make the switch as well.
Please let me know what questions or concerns you have regarding this change.
Thanks and Best Regards, Ildikó
[1]https://lists.openinfra.org/archives/list/foundation@lists.openinfra.org/thr...
———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
Hi StarlingX Community, The OpenStack community is working on the documentation updates to the Contributor Guide to cover the DCO process, you can find the review here: https://review.opendev.org/c/openstack/contributor-guide/+/950839 It came up in earlier discussions that the StarlingX community would prefer to just keep pointing to the OpenStack guides once the DCO enforcement period starts. However, since the DCO process requires ongoing action, as opposed to being a step during the Gerrit account creation process, I would suggest to call out that the StarlingX community adopted the DCO process as well somewhere in the sections that describe the code contribution process. That piece of documentation can still refer to the OpenStack guides that detail what the DCO is, and how to follow the process. What do you think? Thanks, Ildikó
On Jun 11, 2025, at 08:47, Chris Friesen <chris.friesen@windriver.com> wrote:
Thanks for the update, this all sounds reasonable to me.
Chris
On 5/30/2025 5:07 PM, Ildiko Vancsa wrote:
CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi StarlingX community,
I'm reaching out with a quick update.
As you might've already learned from the resources my previous email pointed to, the Contributor License Agreement (CLA) will soon not be applicable to OpenInfra projects. On the last TSC & Community call the TSC and community members briefly discussed next steps and were in an agreement to implement the DCO process as a successor.
Next steps will include: - Updating settings in Gerrit to stop enforcing the CLA - Ildiko + Jeremy - Document the new DCO process, or keep relying on the OpenStack community's guidelines as they become available - Updating any documentation (Contributor Guides, READMEs, etc) in StarlingX that mention the CLA to refer to the new DCO process - StarlingX community - Implement DCO enforcement in Gerrit - Updating config options that are currently used when creating new repos
Please let me know if you have any questions.
Thanks and Best Regards, Ildikó
———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
On May 27, 2025, at 10:13, Ildiko Vancsa <ildiko@openinfra.dev> wrote:
Hi StarlingX community,
I'm reaching out 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 the end of June. It’s something the Board has supported for newer projects, and now existing projects like StarlingX have the opportunity to make the switch as well.
Please let me know what questions or concerns you have regarding this change.
Thanks and Best Regards, Ildikó
[1] https://lists.openinfra.org/archives/list/foundation@lists.openinfra.org/thr...
———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
+1 -----Original Message----- From: Ildiko Vancsa <ildiko.vancsa@gmail.com> Sent: Monday, June 16, 2025 4:46 PM To: starlingx-discuss@lists.starlingx.io Subject: Re: Moving from CLA to DCO for OpenInfra Contributions CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, The OpenStack community is working on the documentation updates to the Contributor Guide to cover the DCO process, you can find the review here: https://review.opendev.org/c/openstack/contributor-guide/+/950839 It came up in earlier discussions that the StarlingX community would prefer to just keep pointing to the OpenStack guides once the DCO enforcement period starts. However, since the DCO process requires ongoing action, as opposed to being a step during the Gerrit account creation process, I would suggest to call out that the StarlingX community adopted the DCO process as well somewhere in the sections that describe the code contribution process. That piece of documentation can still refer to the OpenStack guides that detail what the DCO is, and how to follow the process. What do you think? Thanks, Ildikó
On Jun 11, 2025, at 08:47, Chris Friesen <chris.friesen@windriver.com> wrote:
Thanks for the update, this all sounds reasonable to me.
Chris
On 5/30/2025 5:07 PM, Ildiko Vancsa wrote:
CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi StarlingX community,
I'm reaching out with a quick update.
As you might've already learned from the resources my previous email pointed to, the Contributor License Agreement (CLA) will soon not be applicable to OpenInfra projects. On the last TSC & Community call the TSC and community members briefly discussed next steps and were in an agreement to implement the DCO process as a successor.
Next steps will include: - Updating settings in Gerrit to stop enforcing the CLA - Ildiko + Jeremy - Document the new DCO process, or keep relying on the OpenStack community's guidelines as they become available - Updating any documentation (Contributor Guides, READMEs, etc) in StarlingX that mention the CLA to refer to the new DCO process - StarlingX community - Implement DCO enforcement in Gerrit - Updating config options that are currently used when creating new repos
Please let me know if you have any questions.
Thanks and Best Regards, Ildikó
———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
On May 27, 2025, at 10:13, Ildiko Vancsa <ildiko@openinfra.dev> wrote:
Hi StarlingX community,
I'm reaching out 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 the end of June. It’s something the Board has supported for newer projects, and now existing projects like StarlingX have the opportunity to make the switch as well.
Please let me know what questions or concerns you have regarding this change.
Thanks and Best Regards, Ildikó
[1] https://lists.openinfra.org/archives/list/foundation@lists.openinfra.org/thr...
———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
On 2025-05-27 10:13:49 -0700 (-0700), Ildiko Vancsa wrote:
I'm reaching out 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) [...]
As discussed, tomorrow (2025-07-01) I'll merge https://review.opendev.org/953819 which will switch enforcement to start requiring Signed-off-by in commit messages when pushing new changes or revisions to changes (existing changes don't need to be amended in order to merge, only when revising, rebasing or backporting to other branches). Agreeing to the OpenInfra ICLA will no longer be necessary. After this update merges, when attempting to push or alter a change's content you may receive an error (from git review/git push at the command line or from the Gerrit WebUI if you're trying to edit a change there) notifying you that you're missing a Signed-off-by trailer in your commit message. You can either add one with git's -s option like... git commit -s (to add when making a new commit) git commit --amend -s (when altering an existing commit) ...or by directly editing the commit message to include a line at the end with your address such as... Signed-off-by: Jeremy Stanley <fungi@yuggoth.org> Keep in mind that if you're pushing a series of changes, you may need to update all their commit messages, e.g. through an interactive rebase. If anyone has questions, please don't hesitate to ask! -- Jeremy Stanley
participants (5)
-
Chris Friesen
-
Ildiko Vancsa
-
Ildiko Vancsa
-
Jeremy Stanley
-
Waines, Greg