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 i.e. the criteria for requiring an RFC.
  • Socialize your proposal.
  • Draft your RFC using this template. When ready to iterate, upload your CL and share it broadly to eng-council-discuss@fuchsia.dev. See also creating an RFC.
  • Iterate on your proposal with appropriate stakeholders.
  • As conversations on your proposal converge, and stakeholders indicate their support (+1 on the CL), or their opposition (-1 on the CL), 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.
    • If your RFC is accepted, a member of the Eng Council will comment on your change stating that the RFC is accepted, will assign the RFC a number and mark your change Code-Review +2. Your RFC can now be landed.
    • If your RFC is rejected, a member of the Eng Council will draft a rejection rationale with you for inclusion in the RFC.

Summary of the process (deck)

Proposals

Active RFCs

Gerrit link

Finalized RFCs

RFC area




Accepted

RFC Title Area Gerrit change

RFC-0001

Fuchsia Request for Comments (RFC) process

  • Governance

RFC-0002

Fuchsia platform versioning

  • General

RFC-0003

Fuchsia logging guidelines

  • General

RFC-0004

Units of bytes

  • Governance

RFC-0006

Addendum of the RFC process for Zircon

  • Governance

RFC-0007

Zircon removal of thread killing

  • Kernel

RFC-0008

Remove zx_clock_get and zx_clock_adjust

  • Kernel

RFC-0009

Edge triggered async_wait

  • Kernel

RFC-0010

zx_channel_iovec_t support for zx_channel_write and zx_channel_call

  • Kernel

RFC-0011

zx_object_get_info ZX_INFO_KMEM_STATS_EXTENDED

  • Kernel

RFC-0012

Zircon Discardable Memory

  • Kernel

RFC-0013

Cloning a VMO mapping

  • Kernel

RFC-0014

Relax zx_fifo_create constraints

  • Kernel

RFC-0015

Fuchsia Compatibility Test Suite (CTS)

  • Governance
  • Testing

RFC-0016

Boot time page sizes

  • Kernel

RFC-0017

The FTP Process is dead, long live the RFC Process!

  • FIDL
  • Governance

RFC-0018

FTP process: A modest proposal

  • FIDL
  • Governance

RFC-0019

Using evolution = uint64;

  • FIDL

RFC-0020

Interface ordinal hashing

  • FIDL

RFC-0021

Soft transitions for methods add and remove

  • FIDL

RFC-0022

Clarification: Default values for struct members

  • FIDL

RFC-0023

Compositional model for protocols

  • FIDL

RFC-0024

Mandatory source compatibility

  • FIDL

RFC-0025

Bit flags

  • FIDL

RFC-0027

You only pay for what you use

  • FIDL

RFC-0028

Handle rights

  • FIDL

RFC-0029

Increasing method ordinals

  • FIDL

RFC-0030

FIDL is little endian

  • FIDL

RFC-0033

Handling of unknown fields and strictness

  • FIDL

RFC-0037

Transactional message header v3

  • FIDL

RFC-0040

Identifier uniqueness

  • FIDL

RFC-0041

Support for unifying services and devices

  • FIDL

RFC-0043

Documentation comment format

  • FIDL

RFC-0047

Tables

  • FIDL

RFC-0048

Explicit union ordinals

  • FIDL

RFC-0049

FIDL tuning process evolution

  • FIDL

RFC-0050

FIDL Syntax Revamp

  • FIDL

RFC-0051

Safer structs for C++

  • FIDL

RFC-0052

Type aliasing and new types

  • FIDL

RFC-0053

Epitaphs

  • FIDL

RFC-0054

Parameter attributes

  • FIDL

RFC-0055

Documentation comments

  • FIDL

RFC-0056

Empty structs

  • FIDL

RFC-0057

Default no handles

  • FIDL

RFC-0058

Introduce a deprecated attribute

  • FIDL

RFC-0059

Reserved bits in vector, string, and array count fields

  • FIDL

RFC-0060

Error handling

  • FIDL

RFC-0061

Extensible unions

  • FIDL

RFC-0066

Programmer advisory explicit defaults

  • FIDL

RFC-0067

Additions to Fuchsia RFC process

  • Governance

RFC-0068

Page Eviction Hints

  • Kernel

RFC-0069

Standard I/O in ELF Runner

  • Component Framework

RFC-0070

PCI protocol changes to support legacy interrupts

  • Kernel

RFC-0071

OTA backstop

  • System

RFC-0072

Standalone Image Assembly Tool

  • Build

RFC-0074

Expose Process Start Time

  • Kernel

RFC-0075

Deprecate Zedboot-based paving for provisioning devices

  • General

RFC-0076

FIDL API Summaries

  • FIDL

RFC-0077

zx_clock_update accuracy improvement

  • Kernel

RFC-0078

Kernel Sanitizer Coverage for Fuchsia Fuzzing

  • Kernel

RFC-0079

Detecting debuglog data loss

  • Kernel
  • Diagnostics

RFC-0080

Detecting VMO Immutability

  • Kernel

RFC-0081

fastboot boot

  • General

RFC-0082

Running unmodified Linux programs on Fuchsia

  • PosixCompat

RFC-0083

FIDL versioning

  • FIDL

RFC-0084

Add more metrics to zx_info_task_runtime_t

  • Kernel

RFC-0085

Reducing the zx_status_t space

  • Kernel
  • System

RFC-0086

Updates to RFC-0050: FIDL Attributes Syntax

  • FIDL

RFC-0087

Updates to RFC-0050: FIDL Method Parameter Syntax

  • FIDL

RFC-0089

Core realm variations

  • Component Framework

RFC-0090

Driver shared libraries allowlist

  • Kernel

RFC-0091

zx_system_get_event ZX_SYSTEM_EVENT_IMMINENT_OUT_OF_MEMORY

  • Kernel

RFC-0092

Sessions

  • Sessions

RFC-0093

Design principles of component manifests

  • Component Framework

RFC-0094

Carnelian Virtcon

  • General

RFC-0095

Build and assemble Workstation out-of-tree

  • General

RFC-0096

User input architecture

  • HCI

RFC-0097

FIDL Toolchain

  • FIDL

RFC-0098

Component Framework RFC Criteria

  • Component Framework
  • Governance

RFC-0099

Introduce `zx_socket_set_disposition`

  • Kernel

RFC-0100

Product Metadata

  • Developer

RFC-0101

Dynamic components with numbered handles

  • Component Framework

RFC-0102

Forbid CHILD_NO_WRITE with CHILD_RESIZABLE

  • Kernel

RFC-0103

Software Delivery RFC Criteria

  • Software Delivery
  • Governance

RFC-0104

Relative Component URLs

  • Component Framework

RFC-0105

Regular expression libraries

  • General

RFC-0106

Component manifest includes in the Fuchsia SDK

  • Component Framework

RFC-0107

Dynamic Offers

  • Component Framework

RFC-0108

Component binder protocol

  • Component Framework

RFC-0110

Reboot for termination of critical components

  • Component Framework

RFC-0111

Initial Fuchsia hardware platform specifications

  • Governance

RFC-0112

ACPI support on x86

  • Devices

RFC-0113

Efficient envelopes

  • FIDL

RFC-0114

Inlining small values in FIDL envelopes

  • FIDL

RFC-0115

Build Types

  • System

RFC-0117

Component fuzzing framework

  • Testing

RFC-0118

SWD policy at image assembly

  • Software Delivery

RFC-0119

System-absolute paths considered harmful

  • Build

RFC-0120

Standalone use of the FIDL wire format

  • FIDL

RFC-0121

Component lifecycle events

  • Component Framework

RFC-0122

RFC Stakeholders

  • Governance

RFC-0123

CPU performance info syscalls

  • Kernel

RFC-0124

Decentralized Product Integration: Artifact Description and Propagation

  • General

RFC-0125

Shortlinks on Fuchsia.dev

  • Developer

RFC-0126

Driver Runtime

  • Devices

RFC-0127

Structured Configuration

  • Component Framework

RFC-0128

Introduce `zx_vcpu_kick`

  • Kernel

RFC-0129

Python Support in Fuchsia

  • governance

RFC-0130

Supported Hardware

  • Governance

RFC-0131

Design principles of the FIDL wire format

  • FIDL

RFC-0132

FIDL table size limit

  • FIDL

RFC-0133

Software Delivery Goals

  • Software Delivery

RFC-0134

Software updates time dependency

  • Software Delivery

RFC-0135

Package ABI revisions

  • Software Delivery

RFC-0136

Fxfs

  • Storage

RFC-0137

Discard unknown data in FIDL

  • FIDL

RFC-0138

Handling unknown interactions

  • FIDL

RFC-0139

Bazel SDK

  • General

RFC-0140

Realm Builder

  • Component Framework

RFC-0141

CTS Process

  • Testing

RFC-0142

zx_thread_legacy_yield

  • Kernel

RFC-0143

Userspace Top-Byte-Ignore

  • Kernel

Rejected

RFC Title Area Gerrit change

RFC-0005

Blobfs snapshots

  • Storage

RFC-0026

Envelopes everywhere

  • FIDL

RFC-0031

Typed Epitaphs

  • FIDL

RFC-0032

Efficient envelopes

  • FIDL

RFC-0034

Null terminate strings

  • FIDL

RFC-0035

Automatic flow tracing

  • FIDL

RFC-0036

Update to struct declarations

  • FIDL

RFC-0038

Seperating layout from constraints

  • FIDL

RFC-0039

Types come second

  • FIDL

RFC-0042

Non nullable types

  • FIDL

RFC-0044

Extensible method arguments

  • FIDL

RFC-0045

Zero-size empty structs

  • FIDL

RFC-0062

Method impossible

  • FIDL

RFC-0063

OrdinalRange

  • FIDL

RFC-0064

Box <Knox>

  • FIDL

RFC-0065

No optional strings or vectors

  • FIDL

RFC-0088

Updates to RFC-0050: FIDL Bits, Enum, and Constraints Syntax

  • FIDL

RFC-0116

Wire format support for sparser FIDL tables

  • FIDL

Subscribing to RFCs

You can subscribe for email notifications when new RFCs are uploaded using Gerrit Notifications. A search expression for docs/contribute/governance/rfcs should capture all new RFC changes.

Gerrit settings screenshot demonstrating the
above