Ensure DCO Workflow Check

[peternied]

Coming from opensearch-project/project-meta#17

A Developer Certificate of Origin is required on commits in the OpenSearch-Project.

See doc.yml for an example workflow. Ensure CONTRIBUTING.md to has a section on the DCO per the project template.

• DCO Check Workflow
• CONTRIBUTING.md DCO Section

[vchrombie]

A Developer Certificate of Origin is required on commits in the OpenSearch-Project.

Nice 👍

Even the CHAOSS Charter requires that contributions are accompanied by a Developer Certificate of Origin sign-off. For ensuring it, a bot checks all incoming commits.

See doc.yml for an example workflow.

• DCO Check Workflow

Just wanted to comment about the other options available. The dco bot can be configured at the organization level and it doesn't need any github action workflows.

Example:

• dco failed -> [docker] Add logrotate to docker chaoss/grimoirelab#303
• dco passed -> [docker-compose] Add Filebeat container to ship logs from Mordred to ES chaoss/grimoirelab#293

Please feel free to proceed with whatever option the organization maintainers prefer.
Thanks.

[peternied]

Initially we considered using that DCO bot and choose not to due to its requirement to access private repositories. Instead we built our own check with Jenkins CI for only a handful of repositories, but we never offered an option to smaller repos. This workflow makes it simple to get all our repos in.

[vchrombie]

Okay, thanks for the reply. I think the github actions is the right tool for your usecase. 👍

[peternied]

@vchrombie Can we get the DCO check added on this repo? This is literally the last one in the campaign

[vchrombie]

@vchrombie Can we get the DCO check added on this repo? This is literally the last one in the campaign

Yes, I don't have any problem with it. Please proceed with whatever suits the requirement.
Thanks.