Repository navigation
Clarify WG contribution guidance and harden documentation workflows - #238
Merged
Merged
Conversation
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.
Repair the February 2024 presentation link and June 2025 meeting index, clarify the Working Group's combined specification and implementation scope, and point contributors to an indexed RFC process. Mark the old migration proposal as historical and clarify unverified CI entries without inventing infrastructure availability.
Add contribution, meeting, RFC and security-work-item templates, maintainer-team CODEOWNERS, and local documentation checks. Pin both workflow actions, scope the Slack token to notification steps, set read-only GitHub permissions and timeouts, and trigger RFC notification only when the RFC label itself is added. Keep the existing Slack action version and channel.
Validation: local-link scan passes; link-checker regression tests pass; diff whitespace check passes. Slack trigger conditions are checked without sending a test message. Actual Slack delivery requires a future qualifying event. Existing project obligations and historical records are preserved.