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.
| RFC | Submitted | Reviewed | Title |
|---|---|---|---|
| RFC-0001 | 2020-02-20 | 2020-02-27 | Fuchsia Request for Comments (RFC) process |
| RFC-0002 | 2020-03-30 | 2020-04-23 | Fuchsia Platform Versioning |
| RFC-0003 | 2020-06-03 | 2020-06-10 | Fuchsia Logging Guidelines |
| RFC-0004 | 2020-06-09 | 2020-07-31 | Units of Bytes |
| RFC-0005 | 2020-09-07 | 2020-09-19 | Blobfs Snapshots |
| RFC-0006 | 2020-08-17 | 2020-09-24 | Addendum of the RFC Process for Zircon |
| RFC-0007 | 2020-09-25 | 2020-10-06 | Zircon Removal of Thread Killing |
| RFC-0008 | 2020-10-21 | 2020-10-29 | Remove zx_clock_get and zx_clock_adjust |
| RFC-0009 | 2020-10-22 | 2020-11-04 | Edge triggered async_wait |
| RFC-0010 | 2020-10-01 | 2020-11-06 | zx_channel_iovec_t support for zx_channel_write and zx_channel_call |
| RFC | Submitted | Reviewed | Title |
|---|---|---|---|
| (none) |
