Remove DCO sign-off requirement#32
Draft
jonathanhefner wants to merge 1 commit into
Draft
Conversation
The project does not document or enforce a DCO workflow. Remove the unimplemented sign-off requirement so the governance charter reflects the contribution process contributors actually use.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Remove the sentence requiring a Developer Certificate of Origin (DCO) sign-off for code contributions.
Rationale
The requirement appears to have been inherited from the Open Responses governance charter when that charter was adapted for this project. The project does not otherwise document or enforce a DCO workflow:
CONTRIBUTING.mdcontains no sign-off instructions, there is no automated DCO check, and the repository's commits do not useSigned-off-bytrailers.Removing the sentence makes the charter reflect the contribution process currently in use. It does not change the Apache-2.0 licensing of code, the CC-BY-4.0 licensing of specification text and documentation, or the TSC's authority to approve alternative licenses.
This draft PR is intended to solicit the explicit two-thirds TSC approval required by Section 11 of the charter.
Validation
git diff --check origin/main...HEAD.