tree: 25fa2d48500aa49426ff32ca0b59dedd79f1f352 [path history] [tgz]
  1. 0001_rfc_process.md
  2. 0002_platform_versioning.md
  3. 0003_logging.md
  4. 0004_units_of_bytes.md
  5. 0005_blobfs_snapshots.md
  6. 0005_blobfs_snapshots_fig_1.png
  7. 0005_blobfs_snapshots_fig_2.png
  8. 0005_blobfs_snapshots_fig_3.png
  9. 0005_blobfs_snapshots_fig_4.png
  10. 0006_addendum_to_rfc_process_for_zircon.md
  11. 0007_remove_thread_killing.md
  12. _toc.yaml
  13. OWNERS
  14. README.md
  15. TEMPLATE.md
docs/contribute/governance/rfcs/README.md

Fuchsia RFC process

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.

Note: Documents are sorted by date reviewed.

Accepted proposals

RFCSubmittedReviewedTitle
RFC-00012020-02-202020-02-27Fuchsia Request for Comments (RFC) process
RFC-00022020-03-302020-04-23Fuchsia Platform Versioning
RFC-00032020-06-032020-06-10Fuchsia Logging Guidelines
RFC-00042020-06-092020-07-31Units of Bytes
RFC-00052020-09-072020-09-19Blobfs Snapshots
RFC-00062020-08-172020-09-24Addendum of the RFC Process for Zircon
RFC-00072020-09-252020-10-06Zircon Removal of Thread Killing

Rejected proposals

RFCSubmittedReviewedTitle
(none)   

Process

See RFC-0001: Fuchsia Request for Comments (RFC) process