Add blog post announcing SEP process migration to PRs#1851
Merged
Conversation
pcarleton
reviewed
Nov 20, 2025
pcarleton
reviewed
Nov 20, 2025
dsp-ant
force-pushed
the
sep-process-blog-post
branch
from
cbba22e to
17fe95f
Compare
pcarleton
previously approved these changes
Nov 20, 2025
bdoyle0182
reviewed
Nov 20, 2025
|
|
||
| ## Existing SEPs | ||
|
|
||
| If you have an open SEP as a GitHub issue, don't worry. Existing proposals can continue through their current workflow. However, we encourage new proposals to use the PR-based process going forward. We are moving all implemented SEPs |
There was a problem hiding this comment.
Can we be more explicit on the guidance here? Can existing proposals migrate to this? If not change to existing proposals must
bdoyle0182
reviewed
Nov 20, 2025
|
|
||
| ## What About Status? | ||
|
|
||
| One notable change: **sponsors are now responsible for updating SEP status**. In addition to applying labels to the pull request, the sponsor updates the `Status` field directly in the SEP markdown file. This keeps the canonical state of the proposal in the file itself, versioned alongside the content, while PR labels make it easy to filter and find SEPs by status. |
There was a problem hiding this comment.
since there's many PR's, can we make sure every PR gets the SEP tag for filtering? There's many PR's not tagged with SEP as is prior to this process addition.
Should the direction be that PR creator must include SEP label? And / Or PR naming must follow consistent naming format [SEP-xxx] Name. Currently the PR naming convention isn't consistent
localden
requested changes
Nov 25, 2025
|
|
||
| ## What About Status? | ||
|
|
||
| One notable change: **sponsors are now responsible for updating SEP status**. In addition to applying labels to the pull request, the sponsor updates the `Status` field directly in the SEP markdown file. This keeps the canonical state of the proposal in the file itself, versioned alongside the content, while PR labels make it easy to filter and find SEPs by status. |
Contributor
There was a problem hiding this comment.
Suggested change
| One notable change: **sponsors are now responsible for updating SEP status**. In addition to applying labels to the pull request, the sponsor updates the `Status` field directly in the SEP markdown file. This keeps the canonical state of the proposal in the file itself, versioned alongside the content, while PR labels make it easy to filter and find SEPs by status. | |
| One notable change: **sponsors are now responsible for updating SEP status**. In addition to applying labels to the pull request (such as `SEP` for all submitted SEPs), the sponsor updates the `Status` field directly in the SEP markdown file. This keeps the canonical state of the proposal in the file itself, versioned alongside the content, while PR labels make it easy to filter and find SEPs by status. |
Member
Author
|
Thank you @localden ! I added most of these suggestion and rewrote the post quite a bit. @bdoyle0182 Thank you! I Think since we accepted the SEP without forcing a migration, I'll keep it as is. |
dsp-ant
force-pushed
the
sep-process-blog-post
branch
from
4917bfd to
b8592a9
Compare
- Remove casual "back in" phrasing - Clarify dual numbering issue - Simplify commit instructions for less experienced Git users - Add guidance on preserving discussion history during migration 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <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
4 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.
Summary
Adds a blog post announcing the migration of the SEP process from GitHub issues to pull requests.
Dependencies
This PR is based on #1850 (the SEP process changes) and should be merged after that PR.
Blog Post Contents
Preview
The blog post follows the same tone as existing posts like "Building to Last: A New Governance Model for MCP" - straightforward engineering communication that explains the what, why, and how.
🤖 Generated with Claude Code