docs(rfc): add RFC-000.001 Flutter Architecture & Reference Taxonomy - #1
docs(rfc): add RFC-000.001 Flutter Architecture & Reference Taxonomy#1jtmcdole wants to merge 2 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.
|
Would be nice to have "WANT_LGTM: <list|all>" |
|
We should also consider OKF if we ever wanted to hook these up to a harness. |
zanderso
left a comment
zanderso
left a comment
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.
I welcome another RFC after this one, appropriately numbered, to cover the review process. Issue #3 |
| - 000-meta | ||
| - 600-infrastructure | ||
| authors: | ||
| - codefu@google.com |
There was a problem hiding this comment.
Maybe discourage use of email. Prefer Github username instead?
There was a problem hiding this comment.
I'm OK with either. How strong is "discourage"?
There was a problem hiding this comment.
Pretty strong. Not sure folks want to put their contact info out there to get spammed with, or even worse, potential harrassment.
There was a problem hiding this comment.
I can make that a clear line in the rfc. As someone from Google, I'm OK with my email and name being here, and I'm totally ok with someone leaving a link to their github profile instead.
| - If the proposal spans multiple areas, the shepherd helps identify the **primary** subsystem and ensures secondary areas are listed under `tags:` in frontmatter. | ||
|
|
||
| ### Step 3: Sequential Number Allocation | ||
| - When the RFC enters the **Final Comment Period (FCP)** or is approved for merge: |
There was a problem hiding this comment.
I think we need more structure around this - when is it in FCP? When does that happen? For how long, who manages it, etc.
...but I am about to go look at the second PR. Hold that thought.
There was a problem hiding this comment.
FCP is optional and the Shepard chooses it (or maybe the Forum). Happy to add more, but here we're just saying "When this gets done and before it lands, that's when you number it".
There was a problem hiding this comment.
SGTM! Read PR 2, makes sense!
3 participants
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