You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a7ed625
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: README.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,15 +67,15 @@ The PR's `pulumi preview` comment shows the repository create. Once merged, the
67
67
68
68
The [contributor ladder](https://modelcontextprotocol.io/community/contributor-ladder) ([SEP-2148](https://modelcontextprotocol.io/seps/2148-contributor-ladder)) defines project roles and their privileges. This repo grants access by **team** (roles in [`src/config/roles.ts`](src/config/roles.ts)), not by ladder rank. The table shows how each ladder role corresponds to what is configured here.
69
69
70
-
| Ladder role | Ladder privilege | Configured here |
| Member | Org membership with triage rights |`members` team and `members (synced)` Discord role. The team has `triage` on `modelcontextprotocol`, `docs`, `.github`, `inspector`, `quickstart-resources`, and `servers`, granted per repository rather than through the `all_repo_triage` org role, which would also cover private repositories. Add someone by putting `ROLE_IDS.MEMBERS` in their `memberOf` once the ladder's sponsorship requirements are met. |
74
-
| Maintainer | Merge privileges for owned areas | An "owned area" is a team: SDK teams (under `sdk-maintainers`), `docs-maintainers`, `inspector-maintainers`, `registry-wg`, `reference-servers-maintainers`, and others, each with `push`/`maintain`/`admin` on its repos ([`repoAccess.ts`](src/config/repoAccess.ts)). The general `maintainers` team has `push` on `modelcontextprotocol`. |
75
-
| Core Maintainer | Administrative rights to all MCP repositories |`core-maintainers` holds the `all_repo_admin` org role ([`orgRoles.ts`](src/config/orgRoles.ts)). |
76
-
| Lead Maintainer | All Core Maintainer privileges |`lead-maintainers` holds the `all_repo_admin` org role. Veto and appointment authority are governance, not access. |
77
-
| Community Moderator | Moderation rights on Discord and GitHub Discussions |`moderators` team and Discord role. The team has `maintain` on most community-facing repos. |
78
-
| WG Lead / IG Facilitator | Facilitation and SEP triage; no merge authority by default |`wg-ig-facilitators` Discord role (calendar access). Some WGs have a `*-wg-leads` team with `admin` on the WG's extension repo; most WGs do not. |
70
+
| Ladder role | Ladder privilege | Configured here |
| Member | Org membership with triage rights |`members` team and `members (synced)` Discord role. The team has `push` on `modelcontextprotocol`, so Members can open pull requests there (the repository accepts them from collaborators only, which GitHub defines as write or higher), and `triage` on `docs`, `.github`, `inspector`, `quickstart-resources`, and `servers`. Grants are per repository rather than through the `all_repo_triage` org role, which would also cover private repositories. Add someone by putting `ROLE_IDS.MEMBERS` in their `memberOf` once the ladder's sponsorship requirements are met. |
74
+
| Maintainer | Merge privileges for owned areas | An "owned area" is a team: SDK teams (under `sdk-maintainers`), `docs-maintainers`, `inspector-maintainers`, `registry-wg`, `reference-servers-maintainers`, and others, each with `push`/`maintain`/`admin` on its repos ([`repoAccess.ts`](src/config/repoAccess.ts)). The general `maintainers` team has `push` on `modelcontextprotocol`. |
75
+
| Core Maintainer | Administrative rights to all MCP repositories |`core-maintainers` holds the `all_repo_admin` org role ([`orgRoles.ts`](src/config/orgRoles.ts)). |
76
+
| Lead Maintainer | All Core Maintainer privileges |`lead-maintainers` holds the `all_repo_admin` org role. Veto and appointment authority are governance, not access. |
77
+
| Community Moderator | Moderation rights on Discord and GitHub Discussions |`moderators` team and Discord role. The team has `maintain` on most community-facing repos. |
78
+
| WG Lead / IG Facilitator | Facilitation and SEP triage; no merge authority by default |`wg-ig-facilitators` Discord role (calendar access). Some WGs have a `*-wg-leads` team with `admin` on the WG's extension repo; most WGs do not. |
79
79
80
80
Things to know when reading the config against the ladder:
0 commit comments