add a minimal GOVERNANCE.md for discussion#11
Conversation
Tim Hockin (thockin)
left a comment
There was a problem hiding this comment.
I am OK with this.
|
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:
Reviewer:
Maintainer:
Does that map? Eventually we will want to use OWNERS or CODEOWNERS |
|
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:
Reviewer:
Maintainer:
|
|
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>
ff0568a to
31e7dcc
Compare
- 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)
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.