Skip to content

doc: document the approval process in this repositroy #144

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.

Sign up for GitHub

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

Merged
frewilhelm merged 1 commit into from
Jun 18, 2026
+13 −0
Merged

doc: document the approval process in this repositroy #144

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .github/config/wordlist.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -154,3 +154,4 @@ enablement
stichting
collegial
Hyperledger
dco
12 changes: 12 additions & 0 deletions MAINTAINERS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
# Maintainers

## Approving spec changes

This repository follows the [Community Specification License 1.0](./1._Community_Specification_License-v1.md) and its [Governance Policy](./5._Governance.md).
Two things are required to merge a spec change:

1. **Proof of contribution rights (DCO).** Every commit must be signed off (`Signed-off-by:`), per the [Contributor License Agreement / Section (d) under "In addition"](./.0_CS_Contributor_License_Agreement.md). This is enforced automatically by the DCO check.
2. **Recorded maintainer consensus.** Per [Governance §2.1](./5._Governance.md#2-decision-making), Maintainers determine consensus in good faith and document it. A maintainer review, approval, and merge is that documented evidence.

Consensus is a good-faith judgment, **not** a numeric vote threshold. There is no required percentage and no voting tool
to run. For specification status transitions (Pre-Draft, Draft, Approved) see [Governance §4](./5._Governance.md#4-specification-development-process).
Loading