docs(rfc): add RFC-000.0001 Flutter Architecture & Reference Taxonomy - #1
Open
jtmcdole wants to merge 3 commits into
Open
docs(rfc): add RFC-000.0001 Flutter Architecture & Reference Taxonomy#1jtmcdole wants to merge 3 commits into
jtmcdole wants to merge 3 commits into
Conversation
Establish the architecture taxonomy, numbering scheme, and lifecycle process for Flutter Requests for Comments (RFCs). - Introduce structured identifier format `RFC-AAA.NNN` across 8 core domains (000 Meta through 700 Documentation & Ecosystem). - Define file naming (`rfc/AAA.NNN-kebab-case.md`) and YAML frontmatter schema. - Outline a 4-step assignment lifecycle using `.000` draft placeholders to prevent number collisions during proposal phases. - Specify rules for cross-cutting proposals and number immutability.
Member
Author
|
Would be nice to have "WANT_LGTM: <list|all>" |
Member
Author
|
We should also consider OKF if we ever wanted to hook these up to a harness. |
zanderso
reviewed
Aug 28, 2026
zanderso
left a comment
zanderso
left a comment
Member
There was a problem hiding this comment.
This is a great start. For a complete RFC process we'll also need RFCs that specify the review process, similar to what Slava has in his CL.
Member
Author
I welcome another RFC after this one, appropriately numbered, to cover the review process. Issue #3 |
Member
Author
Piinks
reviewed
Aug 28, 2026
Piinks
reviewed
Aug 28, 2026
zanderso
reviewed
Aug 28, 2026
Leave optional mailbox format
jtmcdole
changed the title
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
3 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.
Establish the architecture taxonomy, numbering scheme, and lifecycle process for Flutter Requests for Comments (RFCs).
AAA.NNNacross 8 core domains (000 Meta through 700 Documentation & Ecosystem).rfc/AAA.NNN-kebab-case.md) and YAML frontmatter schema..000draft placeholders to prevent number collisions during proposal phases.OKFdocument headers for later adoption.fixes: #2