Skip to content

docs(community): add Registry WG charter#2587

Merged
CaitieM20 merged 5 commits into
modelcontextprotocol:mainfrom
tadasant:registry-wg-charter
May 28, 2026
Merged

docs(community): add Registry WG charter#2587
CaitieM20 merged 5 commits into
modelcontextprotocol:mainfrom
tadasant:registry-wg-charter

Conversation

@tadasant

@tadasant tadasant commented Apr 16, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

Summary

  • Adds the initial charter for the Registry Working Group at docs/community/registry/charter.mdx, following the charter template and the conventions used by the existing Server Card, Skills Over MCP, Inspector v2, and Triggers and Events WG charters.
  • Registers the new charter page under the "Working Group Charters" group in docs/docs.json.

Highlights

  • The contents of this charter has been discussed and approved with all of @rdimitrov, @BobDickinson, @domdomegg, @toby, and me
  • We are moving @domdomegg and @toby to Emeritus status
  • @rdimitrov and I move to WG Leads
  • We are welcoming @pree-dew as a new WG Member
  • Our upcoming short term focuses include: alignment with Server Cards, AI automation of triage, AI automation of Registry ops

Tadas Antanavicius and others added 2 commits April 16, 2026 21:27
@claude
docs(community): add Registry WG charter
ce6bcb4 
Formalizes the Registry Working Group's charter covering the registry
service, server.json schema, API specification, client SDKs, publishing
trust model, and adoption outreach.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
@claude
docs(community): add Discord handles and Maintainer column
88468ab 
Co-Authored-By: Claude Opus 4.6 <[email protected]>
@tadasant
tadasant marked this pull request as ready for review April 16, 2026 21:42
@tadasant
tadasant requested review from a team as code owners April 16, 2026 21:42
@claude
docs(community): update Preeti Dewani org and Discord handle
7db18a4 
Organization: Last9 → Ravenmail
Discord: pree_36710 → pree_dew

Co-Authored-By: Claude Opus 4.6 <[email protected]>
@localden

localden commented Apr 17, 2026

Copy link
Copy Markdown
Contributor

@tadasant just to clarify, who is the CM sponsor here?

@tadasant

tadasant commented Apr 19, 2026

Copy link
Copy Markdown
Member Author

@tadasant just to clarify, who is the CM sponsor here?

@localden sorry maybe I missed something, not sure I was aware we wanted formal CM sponsors for landing charters of existing WG's.

These docs don't suggest it for WGs:

Working Group Formation:

  • There must be a widely acknowledged concern requiring coordination
  • PR for creation of WG into docs/community//overview.mdx, gated by CODEOWNERS requiring approval by Maintainers
  • PR for charter into docs/community//charter.mdx, gated by CODEOWNERS requiring approval from Core Maintainers
  • Initial member list approved by WG Lead

Interest Group Formation:

  • Fill out the creation template in the #wg-ig-group-creation channel on Discord
  • A Core Maintainer reviews the proposal; the IG and its Facilitator(s) must be sponsored by at least two Core Maintainers or one Lead Maintainer
  • Once sponsored, the Facilitator(s) organize the IG and create a charter

Should we add A Core Maintainer reviews the proposal; the IG and its Facilitator(s) must be sponsored by at least two Core Maintainers or one Lead Maintainer to the WG section as well?

In any case, @dsp-ant would you be willing to stamp the Registry WG to continue to exist?

@CaitieM20
CaitieM20 merged commit 7d372f2 into modelcontextprotocol:main May 28, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@CaitieM20 CaitieM20 CaitieM20 approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@tadasant @localden @CaitieM20 @olaservo