chore: align registry roster with WG charter#115
Draft
tadasant wants to merge 4 commits into
Draft
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Aligns GitHub access for the Registry with the Registry Working Group charter. Concretely, this introduces a non-maintainer collaborator tier for the registry, adds the first collaborator, and adjusts two existing maintainer rosters.
Changes
New
registry-wg-collaboratorsGitHub team (GitHub-only — no Discord or Google config)roleIds.ts: adds theREGISTRY_WG_COLLABORATORSrole id, annotated// GitHub onlyto match thetypescript-sdk-collaboratorsconvention.roles.ts: defines the role as a GitHub team nested underregistry-maintainers(parent =REGISTRY_MAINTAINERS). Mirrors thetypescript-sdk-collaboratorsmodel — push access, not admin, and no maintainer privileges.repoAccess.ts: grants theregistry-wg-collaboratorsteam push access to theregistryrepo (theregistry-wgmaintainers team keeps admin).Membership updates (
users.ts)registry-wg-collaborators.registry-maintainers; he remains an MCPB maintainer (mcpb-maintainersretained, unchanged).maintainersandregistry-maintainers. His entry is retained with an emptymemberOfand a// Emeritus maintainer of the Registrycomment rather than being deleted. Because he is anexistingGWSUser, no Google Workspace mailbox is created or removed.Notes
Testing
npm test→ 23/23 passing.Logistics
tadasant/accessfork becausetadasantdoes not have push access tomodelcontextprotocol/access. Merging will auto-deploy via Pulumi and requires core-maintainer approval perCODEOWNERS.🤖 Generated with Claude Code