Skip to content

chore: align registry roster with WG charter#115

Open
tadasant wants to merge 5 commits into
modelcontextprotocol:mainfrom
tadasant:chore/registry-roster-charter-alignment
Open

chore: align registry roster with WG charter#115
tadasant wants to merge 5 commits into
modelcontextprotocol:mainfrom
tadasant:chore/registry-roster-charter-alignment

Conversation

@tadasant
Copy link
Copy Markdown
Member

@tadasant tadasant commented May 30, 2026

Summary

Aligns GitHub access for the Registry with the new Registry Working Group charter. Concretely, this introduces a non-maintainer collaborator tier for the registry (registry-collaborators), adds the first collaborator (Pree), and moves Toby and Adam to emeritus Registry maintainership.

Changes

New registry-collaborators GitHub team (GitHub-only — no Discord or Google config)

  • roleIds.ts: adds the REGISTRY_COLLABORATORS role id, annotated // GitHub only to match the typescript-sdk-collaborators convention.
  • roles.ts: defines the role as a GitHub team nested under registry-maintainers (parent = REGISTRY_MAINTAINERS). Mirrors the typescript-sdk-collaborators model — push access, not admin, and no maintainer privileges.
  • repoAccess.ts: grants the registry-collaborators team push access to the registry repo (the registry-wg maintainers team keeps admin).

Membership updates (users.ts)

  • Preeti (Pree) Dewani (@pree-dew) — added as the first member of registry-wg-collaborators.
  • Adam Jones (@domdomegg) — removed from registry-maintainers; he remains an MCPB maintainer (mcpb-maintainers retained, unchanged).
  • Toby Padilla (@toby) — removed from maintainers and registry-maintainers. His entry is retained with an empty memberOf and a // Emeritus maintainer of the Registry comment rather than being deleted. Because he is an existingGWSUser, no Google Workspace mailbox is created or removed.

Notes

  • No Discord config is added for collaborators — there is no corresponding Discord group.
  • This is GitHub-team plumbing only; no Discord roles or Google groups are added or removed by this PR.

Testing

  • npm test23/23 passing.

🤖 Generated with Claude Code

Tadas Antanavicius and others added 5 commits May 30, 2026 23:20
Aligns GitHub teams / Discord roles / Google groups with the Registry
Working Group charter (https://modelcontextprotocol.io/community/registry/charter):

- Add REGISTRY_WG_COLLABORATORS role + registry-wg-collaborators GitHub
  team with push (not admin) on the registry repo, mirroring the
  typescript-sdk-collaborators model. No google config => no
  @modelcontextprotocol.io account (charter: Maintainer? No).
- Add Preeti (Pree) Dewani (@pree-dew) as a registry collaborator.
- Remove Adam Jones (@domdomegg) from REGISTRY_MAINTAINERS (he remains an
  active MCPB maintainer). His @modelcontextprotocol.io account is
  unaffected (existingGWSUser, not managed by this IaC).
- Remove Toby Padilla (@toby) entirely; registry was his only
  maintainership. His @modelcontextprotocol.io account is likewise
  unaffected by this change (existingGWSUser).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Matches the typescript-sdk-collaborators convention in roleIds.ts.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Instead of removing Toby Padilla's access entry entirely, retain it with an
empty memberOf and a comment noting he is an emeritus maintainer of the
Registry.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Drops the '-wg' infix for consistency: GitHub team slug
'registry-wg-collaborators' -> 'registry-collaborators' and the role id
constant REGISTRY_WG_COLLABORATORS -> REGISTRY_COLLABORATORS, keeping the
constant and slug mirrored as with typescript-sdk-collaborators.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@tadasant tadasant marked this pull request as ready for review June 1, 2026 02:20
@tadasant tadasant requested a review from a team as a code owner June 1, 2026 02:20
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.

1 participant