legal: human content and dco #198
Open
+63
−0
Conversation
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
Signed-off-by: Wesley Bryie (SideStore) <[email protected]>
polymo1
requested review from
a team,
JoeMatt,
Spidy123222,
SternXD,
lonkelle and
nythepegasus
as code owners
neoarz
approved these changes
Jan 2, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hello all,
I am proposing to add the Human Content Statement and Developer Certificate of Origin to the documentation.
The Human Content Statement is non-negotiable, but I am open to amending it. The Developer Certificate of Origin is negotiable, however it cannot be changed.
Both documents will only take precedent upon the merging of the PR, and all changes would be expected to follow both documents exactly.
I am requesting your opinions on these documents, as you are the ones who contribute to the project with your time.