{{ message }}
Restructure Security IG as a routing group - #3331
Open
claude[bot] wants to merge 3 commits into
Open
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews. 💡 Tip: Enable Workflows to automatically generate PRs for you. |
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
1 participant
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 Security IG charter described a group that catalogs threats, reviews proposals, and scopes validated problems into Working Groups or SEPs, meeting in biweekly office hours with an agenda shared ahead of each call. The security policy page described the IG as the venue for discussing threats and proposals.
After: The charter now presents the IG as the first stop for MCP-specific security topics. It vets incoming threats, proposals, and disclosure questions, then routes validated work to the owning group. Triage and routing is added to the In Scope list, discussion runs asynchronously in
#security-ig, and the biweekly office hours are replaced with agenda-driven forum calls plus a monthly digest. The security policy page is updated to match. Scope, leadership, and membership are otherwise unchanged.This reflects the decision recorded in item 4 of the Aug 26 core maintainer meeting notes, discussion #3316, which converted the dormant standing call into a routing group with an open forum model.
npm run preppasses clean.Generated by Claude Code