chore: Clarify process for API WG approval of RFCs #23
+11
−3
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
Our RFC approval process has required some tweaks over time, because presenting to a quorum of the WG has proved challenging due to member timezones and engagement levels. This PR documents a simple majority of API WG sign-offs as the requirement for approval, and describes the presentation of the RFC in a synchronous meeting as an optional step when asynchronous PR feedback is insufficient.
itsananderson
changed the title
samuelmaddock
approved these changes
Oct 25, 2025
jkleinsc
approved these changes
Oct 31, 2025
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.
Our RFC approval process has required some tweaks over time, because presenting to a quorum of the WG has proved challenging due to member timezones and engagement levels.
This PR documents a simple majority of API WG sign-offs as the requirement for approval, and describes the presentation of the RFC in a synchronous meeting as an optional step when asynchronous PR feedback is insufficient.