-
Notifications
You must be signed in to change notification settings - Fork 444
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
Add DCO description to the contribution guidelines. #4743
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Might want to add an example command line Also, your commit does not have DCO :-) |
Currently looking into ways to make this more convenient. Unfortunately, it looks like the inconvenience is by design. There is no git configuration that allows you to sign your commits automatically. Fwiw the failing CI test contains instructions on how to fix the commit, too.
Yes, intentionally! I am trying a configuration option that lets you sign a PR retroactively. |
It looks like there is currently no way around signing every commit. At the same time you can not automate your local git config to always add |
You could recommend people use a Bash alias like |
I have not tried this, but if it works, perhaps you would consider it less onerous? |
This would be a local git hook every user has to set up for their repository. But this document seems quite useful in general, maybe we can copy it. |
Is this an alternative to CLA, or is this in addition to it? What is the reason behind the change? I could have easily missed something as I did not pay attention lately, but I thing the PR itself should describe what is going on as this could have significant impact on downstream development, especially where the CLA is handled by Corporations' legal department. |
DCO will be replacing CLA, and we will migrate slowly.
To simplify the contribution process by eliminating the need for manager approval for company contributions. |
Basically what Adarsh said. It replaces the CLA. I made a little writeup here but we will broadcast on the mailing lists too once it is rolled out on every repository: Still trying to figure out how to make signed commits convenient... |
Signed-off-by: fruffy <fruffy@nyu.edu>
Signed-off-by: fruffy <fruffy@nyu.edu>
Signed-off-by: fruffy <fruffy@nyu.edu>
Signed-off-by: fruffy <fruffy@nyu.edu>
Adding a commit hook like this appears to be the most convenient option for DCO: |
Now that we are part of the Linux foundation we will switch away from the ONF CLA to DCO for Github pull requests and contributions. DCO is the main mode of license management for LF projects. The nice part is that, compared to the ONF CLA, it does not require manager approval for company contributions. This should greatly simplify the contribution process.
We will selectively enable DCO on some repositories to test it. Nothing much should change for contributors. The only thing that is necessary is to sign your commits on PRs with Signed-off-by: .
https://github.com/src-d/guide/blob/master/developer-community/fix-DCO.md
Provides good tips on how to manage contributing to a DCO repository. Commit hooks are the easiest mechanism to automate signoff.