Skip to content

add a minimal GOVERNANCE.md for discussion#11

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

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

Conversation

@dims
Copy link
Copy Markdown
Collaborator

@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.

Comment thread .github/CODEOWNERS Outdated
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 Outdated
Comment thread GOVERNANCE.md Outdated
@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 Outdated
@thockin
Copy link
Copy Markdown
Collaborator

Tim Hockin (thockin) commented May 21, 2026

Thinking more, let's ignore org membership for now, until we figure it out a bit more.

Default: not an org member or repo collaborator

Contributor:

  • Made at least 1 non-trivial contribution and is known to / vouched for by other maintainers: +Repo:Read
  • Made "enough" contributions (decided among maintainers): +Repo:Read

Reviewer:

  • Made "enough" contributions (decided among maintainers) and vouched for by 2 maintainers: +RepoTriage

Maintainer:

  • Made "enough" contributions (decided among maintainers) and vouched for by 2 maintainers: +RepoWrite

@thockin
Copy link
Copy Markdown
Collaborator

Do we need to codify those rules in this doc instead of "voting"?

Signed-off-by: Davanum Srinivas <davanum@gmail.com>
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
- Drop .github/CODEOWNERS — defer to a separate discussion per
  agent-substrate#11 (comment)
- Fix mailing list address: groups.google.com -> googlegroups.com per
  agent-substrate#11 (comment)
- Codify a four-tier role model (Default / Contributor / Reviewer /
  Maintainer) with Read / Triage / Write permission mapping and a
  "enough contributions + 2 Maintainer vouches" promotion criterion,
  per thockin's 2026-05-21 proposal in
  agent-substrate#11 (comment)
- Replace "majority / 2/3 supermajority of Maintainers" language with
  "Maintainer support / approval" and note that authority will be
  delegated to per-subsystem owners as the project grows, per
  agent-substrate#11 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants