Skip to content

Require WG/IG discussion before SEP submission - #3336

Merged
localden merged 4 commits into
mainfrom
require-wg-ig-sep-discussion
Sep 28, 2026
Merged

localden merged 4 commits into
mainfrom
require-wg-ig-sep-discussion

Conversation

@claude

@claude claude Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Requested by Den Delimarsky · Slack thread

Before: The SEP guidelines mention discussing an idea with the relevant working or interest group only as a tip inside a Note, so a SEP can be submitted without any prior community discussion.

After: Prior discussion with the relevant working or interest group in Discord is a requirement. SEP authors discuss the idea with the group before opening the SEP PR and link that discussion in the PR description (a Discord thread, WG/IG meeting notes, or a GitHub Discussion), with #general or GitHub Discussions as the fallback when no relevant group exists. The sponsor confirms the discussion happened and is linked before moving a SEP to in-review. The FAQ on the working and interest groups page and the Specification Proposal Guidelines in CONTRIBUTING.md state the same rule.

How: docs/community/sep-guidelines.mdx turns the Note's discussion bullet into a normative paragraph above the numbered steps and adds a new step 1 "Discuss with the relevant group", renumbering the rest. The sponsor check is one added sentence in the formal review step. No new SEP preamble fields. docs/community/working-interest-groups.mdx changes only the "Do I need to be in a WG to submit a SEP?" answer. CONTRIBUTING.md adds one sentence linking to the guidelines.


Generated by Claude Code

@claude
claude Bot requested review from a team as code owners September 1, 2026 05:49
@mintlify

mintlify Bot commented Sep 1, 2026 •

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
mcp-staging 🟢 Ready View Preview Sep 28, 2026, 10:04 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@mintlify

mintlify Bot commented Sep 1, 2026 •

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
mcp 🟢 Ready View Preview Sep 28, 2026, 10:04 PM

💡 Tip: Enable Automations to automatically generate PRs for you.


2. **Create a pull request** adding your SEP file to the `seps/` directory in the [specification repository](https://github.com/modelcontextprotocol/modelcontextprotocol).
3. **Create a pull request** adding your SEP file to the `seps/` directory in the [specification repository](https://github.com/modelcontextprotocol/modelcontextprotocol).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@claude keep in mind that now the repository is restricted to PRs from collaborators only.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated step 3 to state the restriction. It now ends with: "The repository accepts pull requests from collaborators only."


Generated by Claude Code

Resolves the conflict in docs/community/sep-guidelines.mdx by keeping
the branch's step numbering (Finalization as step 10) and taking main's
added sentence about the published SEP index.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CSauKSAXXGrouGbnSs4yst
@localden
localden merged commit b3e2cc7 into main Sep 28, 2026
9 checks passed
@localden
localden deleted the require-wg-ig-sep-discussion branch September 28, 2026 22:47

This branch was successfully deployed

1 active deployment
staging - docs — 397818ef Deployed Sep 28, 2026 by mintlify[bot]
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.

3 participants