Skip to content

SEP-1302: Formalize Working Groups and Interest Groups in MCP Governance#1350

Merged
olaservo merged 11 commits intomodelcontextprotocol:mainfrom
tadasant:tadasant/sep-1302
Sep 23, 2025
Merged

SEP-1302: Formalize Working Groups and Interest Groups in MCP Governance#1350
olaservo merged 11 commits intomodelcontextprotocol:mainfrom
tadasant:tadasant/sep-1302

Conversation

@tadasant
Copy link
Copy Markdown
Member

PR of #1302 for easier commenting on details.

dend
dend previously requested changes Sep 11, 2025
Comment thread MAINTAINERS.md Outdated
Comment thread MAINTAINERS.md
Comment thread docs/community/governance.mdx
Comment thread docs/community/governance.mdx Outdated
Comment thread docs/community/governance.mdx Outdated
Comment thread docs/community/working-interest-groups.mdx Outdated
Comment thread docs/community/working-interest-groups.mdx Outdated
Comment thread docs/community/working-interest-groups.mdx Outdated
Comment thread docs/community/working-interest-groups.mdx Outdated
Comment thread docs/community/working-interest-groups.mdx Outdated
@dend
Copy link
Copy Markdown
Contributor

dend commented Sep 11, 2025

@tadasant love the work that you're doing here! Should we also include #1401 here as well, linking to existing IG/WG meeting links and notes (tagged from GitHub issues)?

cc: @olaservo

tadasant and others added 2 commits September 11, 2025 09:25
Co-authored-by: Den Delimarsky <hi@den.dev>
@tadasant
Copy link
Copy Markdown
Member Author

@dend thank you for the thorough review! Accepted most of your suggestions, a couple minor followups inline.

@tadasant love the work that you're doing here! Should we also include #1401 here as well, linking to existing IG/WG meeting links and notes (tagged from GitHub issues)?

I'm not opposed to adding that though that feels like a chunk of work that doesn't require net new decisions worth including in the SEP process. So in the interest of limiting scope for this SEP, I think we can track that separately from this PR?

@tadasant
Copy link
Copy Markdown
Member Author

@tadasant @dend Is it possible for us to include/establish a WebMCP working group? This is being proposed as a web standard by the W3C Web Machine Learning Working Group with backers from Microsoft, Google, etc.

It would be beneficial to open a bridge between the two communities to ensure that learnings are shared. Please also let me know who to reach out to in order to add a community channel within the contributors discord server.

Hi @MiguelsPizza - I think the quickest path here is for this SEP to land (I expect clarity on it within ~1.5 weeks) and then use the process outlined for creation of new IG/WG's to make your pitch (FWIW: sounds like a good idea to me to make that a WG).

@dend dend added SEP draft SEP proposal with a sponsor. labels Sep 14, 2025
@dend
Copy link
Copy Markdown
Contributor

dend commented Sep 14, 2025

Thank you @tadasant - are you ready to put this for review? 😊

@MiguelsPizza +1 to what @tadasant mentioned above - once the SEP merges, you should follow the outlined process to work through a WG/IG creation (since logistically your ask is less related to the SEP itself 😊)

@tadasant
Copy link
Copy Markdown
Member Author

Thank you @tadasant - are you ready to put this for review? 😊

Yep let's do it @dend!

@localden localden added accepted SEP accepted by core maintainers, but still requires final wording and reference implementation. and removed draft SEP proposal with a sponsor. labels Sep 17, 2025
@localden
Copy link
Copy Markdown
Contributor

Confirming that this SEP was accepted by the Core Maintainers earlier today - we'll work with @tadasant to update the verbiage where needed and get this in merge-able shape.

@tadasant
Copy link
Copy Markdown
Member Author

Confirming that this SEP was accepted by the Core Maintainers earlier today - we'll work with @tadasant to update the verbiage where needed and get this in merge-able shape.

Do you have specific parts of this in mind that you want me to spend some more time with? I did an end-to-end read recently and IMO it could be good to merge as-is (at which point I will start actioning all the Discord changes and nudges to converge on this IG/WG paradigm), but I know we have some pending comment threads. Let me know how you'd like to proceed.

@localden localden dismissed dend’s stale review September 23, 2025 06:39

Changes merged.

@localden
Copy link
Copy Markdown
Contributor

@olaservo @ihrpr - can you please approve so we can merge? 😄

@olaservo olaservo merged commit e673bb7 into modelcontextprotocol:main Sep 23, 2025
2 checks passed
@tadasant
Copy link
Copy Markdown
Member Author

Thanks all - I will make moves on actioning the impacts of this in Discord this week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

accepted SEP accepted by core maintainers, but still requires final wording and reference implementation. SEP

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants