{{ message }}
Align WG/IG creation docs with the de-facto charter flow - #3284
Merged
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012ujLL8MSZA6F1apWiwQQ9b
|
Preview deployment for your docs. Learn more about Mintlify Previews. 💡 Tip: Enable Workflows to automatically generate PRs for you. |
dsp-ant
approved these changes
Aug 20, 2026
9 tasks
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
2 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 David Soria Parra · Slack thread
Before: the Lifecycle section of
docs/community/working-interest-groups.mdxprescribes a two-step process — a proposal PR atdocs/community/working-groups/<name>/overview.mdxfollowed by a separate charter PR at<name>.mdx— that no group has ever used. The charter template and all 15+ existing groups use a single flat charter file (docs/community/working-groups/<name>.mdxordocs/community/interest-groups/<name>.mdx) plus a nav entry indocs/docs.json.After: the docs describe the actual flow — one charter PR written from the charter template, adding the flat
<name>.mdxfile and the correspondingdocs/docs.jsonnavigation entry, gated by CODEOWNERS requiring Core Maintainer approval. The IG formation step now spells out the same path. All governance semantics (sponsorship, approval authorities, retirement, the IG Discord-template step) are unchanged.This contradiction surfaced while reviewing #3282, whose author followed the
overview.mdxpath the docs currently prescribe.npm run check:docspasses (format, comments, broken links).🤖 Generated with Claude Code
https://claude.ai/code/session_012ujLL8MSZA6F1apWiwQQ9b
Generated by Claude Code