{% include “docs/contribute/governance/rfcs/_common/_rfc_header.md” %}
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 is detailed in RFC-0001: Fuchsia Request for Comments process, along with RFC-0006: Addendum of the RFC process for Zircon.
Criteria for requiring an RFC is detailed in RFC-0001.
The following kinds of changes must use the RFC process.
In addition, changes in the source directories:
/zircon
/src/zircon
/src/bringup
that meet the following criteria must use the RFC process as described in RFC0006: Addendum of the RFC Process for Zircon.
Once you are familiarized with the RFC guidelines and area ready to send an RFC proposal for review, see Creating a RFC.
Accepted {% include “docs/contribute/governance/rfcs/_common/_index_table_header.md” %} {% for rfc in rfcs %} {% if rfc.status == “Accepted” %} {% include “docs/contribute/governance/rfcs/_common/_index_table_body.md” %} {% endif %} {% endfor %} {% include “docs/contribute/governance/rfcs/_common/_index_table_footer.md” %}
Rejected {% include “docs/contribute/governance/rfcs/_common/_index_table_header.md” %} {% for rfc in rfcs %} {% if rfc.status == “Rejected” %} {% include “docs/contribute/governance/rfcs/_common/_index_table_body.md” %} {% endif %} {% endfor %} {% include “docs/contribute/governance/rfcs/_common/_index_table_footer.md” %}
{# This div is used to close the filter that is initialized above #}