Repository navigation
Document RFC 001 provenance without inferring approval - #244
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.
Link RFC 001 to its original PR 86 and recorded merge date. Distinguish the documented merge from formal approval or supersession of its separate-organization recommendation. Preserve the original proposal and point readers to current project locations.
Evidence: PR 86 was merged February 20, 2025; its visible discussion addresses naming and contains no explicit final disposition of that recommendation.
Validation: local file and section links, document structure and whitespace checks pass. No PDFs changed. Required GitHub checks must pass before merge.
The user authorized pushing and merging after checks; use the existing administrator review exception. This is not independent CODEOWNER approval or a new RFC decision.