Remove the DCO requirement for commits #714
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: James Couball <jcouball@yahoo.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Remove the requirement for DCO sign-off.
This project has implemented an automated check for the presence of a sign-off but nothing to check it's authenticity or the contributor's understanding. In order to provide the intended robust legal protection, a mechanism would have to be put into place to track that contributors have understood what putting the sign-off in the commit message and add them to a "committer whitelist".
Truffle Ruby, for example, requires that all contributors sign an Oracle Contributor Agreement before they are allowed to contribute to their repository.
Rather than implement a more formalized and heavier process to track these attestations, DCO shall be removed from this project.
In my experience, this is the way that most OpenSource Ruby project operate.