-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Applying DCO to all devfile repositories #878
Comments
elsony
changed the title
Applying DCO to repositories
Applying DCO to all devfile repositories
Jun 21, 2022
3 tasks
3 tasks
docker-plugin left |
Closing in favor of #1618 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Which area/kind this issue is related to?
/area api
/area library
/area registry
/area devworkspace
/area integration-tests
/area test-automation
NOTE: This also applies to the product registry.
Issue Description
Applying DCO to all devfile repositories:
add a file to the root directory of your project repository containing just the text of version 1.1 of the DCO (example: https://github.com/metal3-io/metal3-docs/blob/master/DCO).
add the following text to a CONTRIBUTING.md file in the root directory of your project repository:
Certificate of Origin
By contributing to this project you agree to the Developer Certificate of
Origin (DCO). This document was created by the Linux Kernel community and is a
simple statement that you, as a contributor, have the legal right to make the
contribution. See the DCO file for details.
Background Info:
With the recent Github announcement about enabling DCO (Developer Certificate of Origin) sign offs, the architects team discussed enabling this new feature in all our github repos, so as to be consistent.
Please document DCO practice in your repo
DCO basically is a way for a contributor to express they can contribute to a project, according to the project's licensing requirements. It signifies that the contributor has the right to submit the contribution under the applicable open source license of the project.
The text was updated successfully, but these errors were encountered: