Skip to content

add a minimal GOVERNANCE.md for discussion#11

Open
Davanum Srinivas (dims) wants to merge 2 commits into
agent-substrate:mainfrom
dims:add-governance
Open

add a minimal GOVERNANCE.md for discussion#11
Davanum Srinivas (dims) wants to merge 2 commits into
agent-substrate:mainfrom
dims:add-governance

Conversation

@dims
Copy link
Copy Markdown
Contributor

@dims Davanum Srinivas (dims) commented May 20, 2026

Howdy folks! Thanks for the awesome work :) I hear you may be open to some of us eager to help out. Here's my bit to get started.

NOTE: we don't yet have a .github/CODEOWNERS

Added one :)

Signed-off-by: Davanum Srinivas <davanum@gmail.com>
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
Comment thread .github/CODEOWNERS
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's make CODEOWNERS / OWNERS a different discussion?

Copy link
Copy Markdown
Collaborator

@thockin Tim Hockin (thockin) left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment thread GOVERNANCE.md
@@ -0,0 +1,32 @@
# Governance

> **Status: Draft — under review and discussion.** This document is a proposal and has not yet been ratified by the Substrate maintainers. Feedback welcome via PR review or on the `ate-dev@groups.google.com` mailing list.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment thread GOVERNANCE.md

- **Code changes.** Every PR needs at least one Maintainer approval and green CI before merge. Authors do not merge their own PRs.
- **Design changes.** File a GitHub issue or discussion describing the proposal and tag relevant Maintainers. Allow at least one week for feedback. Significant changes require majority Maintainer support.
- **Disputes.** Try to resolve on the PR or issue first. If that fails, any participant can ask the Maintainers to decide; Maintainers resolve by majority vote.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is OK for now, but hopefully we will see more direct ownership of subsystems which will delegate authority away from "majority" votes.

@thockin
Copy link
Copy Markdown
Collaborator

To clarify, AIUI we have two distinct places where we can apply "authority":

Org: Member / Owner

Repo: Read / Triage / Write / Maintain / Admin

I think we should distinguish "project administration" from "development" from the beginning, so Org:Owner, Repo:Maintain, and Repo:Admin are put aside for now.

This doc proposes 3 tiers: Contributors, Reviewers, Maintainers. There's an implicit tier below contributors ("contributor to be").

Default: not an org member or repo collaborator

Contributor:

  • Sent 1 PR and is known to other org members: +Repo:Read
  • Sent "enough" PRs (TBD among org members): +Repo:Read
  • Sent "enough" PRs and vouched by 2 org members: +Org:Member

Reviewer:

  • Sent "enough" PRs and vouched by 2 org members: +RepoTriage

Maintainer:

  • Sent "enough" PRs and vouched by 2 org members: +RepoWrite

Does that map? Eventually we will want to use OWNERS or CODEOWNERS

Comment thread GOVERNANCE.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants