Require WG/IG discussion before SEP submission - #3336
Open
claude[bot] wants to merge 3 commits into
Open
claude[bot] wants to merge 3 commits into
claude[bot] wants to merge 3 commits into
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
localden
requested changes
Sep 10, 2026
|
|
||
| 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). | ||
|
|
Contributor
There was a problem hiding this comment.
@claude keep in mind that now the repository is restricted to PRs from collaborators only.
Contributor
Author
There was a problem hiding this comment.
Updated step 3 to state the restriction. It now ends with: "The repository accepts pull requests from collaborators only."
Generated by Claude Code
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CSauKSAXXGrouGbnSs4yst
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
3 participants
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.
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
#generalor GitHub Discussions as the fallback when no relevant group exists. The sponsor confirms the discussion happened and is linked before moving a SEP toin-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.mdxturns 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.mdxchanges only the "Do I need to be in a WG to submit a SEP?" answer.CONTRIBUTING.mdadds one sentence linking to the guidelines.Generated by Claude Code