Fuchsia RFCs

The Fuchsia RFC process is intended to provide a consistent and transparent path for making project-wide, technical decisions. For example, the RFC process can be used to evolve the project roadmap and the system architecture.

The RFC process evolves over time, and can be read here in its detailed current form. It is also summarized below.

Summary of the process

• Review when to use the process.
• Socialize your proposal.
• Draft your RFC using this template and share with stakeholders. See creating an RFC and RFC best practices.
• As conversations on your proposal converge, and stakeholders indicate their support, email eng-council@fuchsia.dev to ask the Eng Council to move your proposal to Last Call.
• After a waiting period of at least 7 days, the Eng Council will accept or reject your proposal, or ask that you iterate with stakeholders further.

For detailed information, follow the RFC process.

Summary of the process (deck)

Stay informed

You can configure Gerrit Notifications to email you when new RFCs are uploaded.

Include the docs/contribute/governance/rfcs search expression and select Changes to receive email notifications for each new RFC proposal.

List of all RFCs

For the full list of all RFCs, see List of all Fuchsia RFCs.