Honoring Asian Pacific American Heritage Month. See how.

Get involved with Fuchsia

This document describes the different ways you can get involved and stay informed about Fuchsia.

Review the Fuchsia roadmap

The Fuchsia project prioritizes features and enhancements that support our development community. Read the Fuchsia roadmap to get a high-level understanding of the various projects being considered within Fuchsia.

Understand the Request for Comments (RFC) process

The Requests for Comments (RFC) process is intended to provide a consistent and transparent path for making project-wide technical decisions.

RFCs are documents that inform and build on the technical direction of the Fuchsia project. RFCs can be proposed by anyone in the community. Using an RFC, a Fuchsia community member can submit an idea or technical concept for broader review or consideration. For more information, see Fuchsia RFCs.

Review completed RFCs

To see a complete list of accepted and rejected RFC proposals, see Accepted proposals and Rejected proposals.

Track ongoing RFCs

To stay up-to-date with RFCs that are still in progress, you can bookmark this saved search that lists any open Gerrit change in the rfcs directory.

Create an RFC

If you want to create a proposal that you want the Fuchsia Eng Council to review, see Creating an RFC.

Join a discussion group

Stay informed about the Fuchsia project by joining a discussion group.

General discussion

The following are general Fuchsia discussion groups:

Group Purpose
announce A read-only list for announcements about Fuchsia.
discuss For general conversation about Fuchsia.
Discord community Fuchsia's Discord community.
testability-discuss Discussion list for general conversation about testable code and Fuchsia’s testability rubrics.

Topic discussion

The following discussion groups are for specific areas of Fuchsia:

Group Purpose
a11y-dev For conversation about accessibility on Fuchsia.
audio-dev For conversation about audio on Fuchsia.
camera-dev Discussions about the development of Fuchsia's camera APIs.
component-framework-dev For conversation about Component Framework, Session Framework, and Modular.
connectivity-dev For conversation about connectivity and networking on Fuchsia.
diagnostics-dev Discussions about the development of diagnostics features and services, such as Inspect, Logs, and the Archivist.
docs-discuss For conversation about about documentation on fuchsia.dev.
drivers-dev For conversation about drivers .
fidl-dev For conversation about FIDL .
graphics-dev For conversation about graphics on Fuchsia.
intl-dev For conversation about internationalization and localization on Fuchsia.
media-dev For conversation about media and playback on Fuchsia.
pkg-dev For conversation about Package .
sdk-dev For conversation about the Fuchsia IDK , formerly called the Fuchsia SDK.
security-dev For conversation about Fuchsia’s security architecture.
session-framework-dev For conversation about Session framework .
storage-dev For conversation about filesystems and other storage concerns on Fuchsia.
toolchain-dev For conversation about Fuchsia’s C/C++, Go, and Rust toolchain support.
rust-users Discussion list specifically for Rust toolchain support in Fuchsia.
ui-input-dev Discussion list for those working on user input events.
zircon-dev For conversation about Zircon .

Platform governance and management

The following discussion groups are for communicating with Fuchsia’s leadership:

Group Purpose
api-council Discussion list for communicating with the Fuchsia API Council.
community-managers Inbound-only discussion list for contacting Fuchsia’s Community Managers with concerns or questions.
eng-council Discussion list for communicating with the Fuchsia Eng Council about review requests, RFC feedback, or RFC escalations.
eng-council-discuss Discussion list for communicating with the Fuchsia Eng Council.

Contribute code

The Fuchsia project encourages well-tested, high-quality contributions from anyone who wants to contribute to Fuchsia, not just from Googlers.

To learn more about how to contribute a code change to Fuchsia, see Contribute changes.

Report an issue

Did you see a line of documentation or code that you think needs to be improved? You can help get these kinds of concerns resolved by filing an issue in Monorail. For more information, see Report an Issue.

All participation in groups, bugs, and forums must adhere to the Fuchsia Code of Conduct. Report Code of Conduct issues directly to the Community Management team via:

  • Email
  • Discord, via the @Community Managers role, or to any individual Community Manager (identified by that role) via direct message.
  • A Monorail ticket. Note that such tickets are only visible to Community Managers.