Repository navigation
Add guidance to discuss SEPs with working groups before submission - #2358
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
SamMorrowDrums
left a comment
SamMorrowDrums
left a comment
Contributor
There was a problem hiding this comment.
This is great, but I would maybe also link to working group docs and is there a way to do a permalink to core maintainer priorities? I feel like it would be good to somehow clarify that:
- discussing with ig/wg first is top priority
- if there is no relevant group you can share with the general working group and it may be the case that a new group is worth standing up if nothing suitable exists (perhaps noting that there's a lot of work involved in getting sponsors and facilitators, which is still
preferable to a cold submission and a good test whether an idea is able to garner sufficient traction) - alignment with core maintainer priorities is also worth checking, because non-urgent changes outside those priorities also adds likely delay/friction.
…roup, and core maintainer priority alignment Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
…s, link to IG/WG creation docs Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Contributor
Author
|
@SamMorrowDrums added some clarification - thank you for the feedback! |
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
dend
enabled auto-merge
March 5, 2026 20:49
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
localden
approved these changes
Mar 5, 2026
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
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
Test plan
/community/communication#discordresolves properly🤖 Generated with Claude Code