| # 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](/docs/contribute/roadmap.md) |
| 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](/docs/contribute/governance/rfcs). |
| |
| ### Review completed RFCs |
| |
| To see a complete list of accepted and rejected RFC proposals, see [Accepted proposals](/docs/contribute/governance/rfcs#accepted) |
| and [Rejected proposals](/docs/contribute/governance/rfcs#rejected). |
| |
| ### Track ongoing RFCs |
| |
| To stay up-to-date with RFCs that are still in progress, you can bookmark this [saved search](https://fuchsia-review.googlesource.com/q/dir:docs/contribute/governance/rfcs+is:open) |
| 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.](/docs/contribute/governance/rfcs/create_rfc.md) |
| |
| ## Join a mailing list |
| |
| Stay informed about the Fuchsia project by joining mailing lists. |
| |
| ### General discussion |
| |
| The following are general Fuchsia mailing lists: |
| |
| |
| <table> |
| <tr> |
| <td><strong>Mailing list</strong> |
| </td> |
| <td><strong>Purpose</strong> |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/announce">announce</a> |
| </td> |
| <td>A read-only list for announcements about Fuchsia. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/discuss">discuss</a> |
| </td> |
| <td>For general conversation about Fuchsia. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/testability-discuss">testability-discuss</a> |
| </td> |
| <td>Discussion list for general conversation about testable code and Fuchsia’s testability rubrics. |
| </td> |
| </tr> |
| </table> |
| |
| ### Topic discussion |
| |
| The following mailing lists are discussion channels for specific areas of |
| Fuchsia: |
| |
| <table> |
| <tr> |
| <td><strong>Mailing list</strong> |
| </td> |
| <td><strong>Purpose</strong> |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/a11y-dev">a11y-dev</a> |
| </td> |
| <td>For conversation about accessibility on Fuchsia. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/audio-dev">audio-dev</a> |
| </td> |
| <td>For conversation about audio on Fuchsia. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/camera-dev">camera-dev</a> |
| </td> |
| <td>Discussions about the development of <a href="/reference/fidl/fuchsia.camera/index.md">Fuchsia's camera APIs</a>. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/component-framework-dev">component-framework-dev</a> |
| </td> |
| <td>For conversation about <a href="/docs/glossary.md#component-framework">Component Framework</a>. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/connectivity-dev">connectivity-dev</a> |
| </td> |
| <td>For conversation about connectivity and networking on Fuchsia. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/diagnostics-dev">diagnostics-dev</a> |
| </td> |
| <td> |
| Discussions about the development of diagnostics features and services, such as |
| <a href="/docs/development/diagnostics/inspect/README.md">Inspect</a>, |
| <a href="/docs/concepts/diagnostics/logs/README.md">Logs</a>, and the Archivist. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/drivers-dev">drivers-dev</a> |
| </td> |
| <td>For conversation about <a href="/docs/glossary.md#driver">Drivers</a>. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/fidl-dev">fidl-dev</a> |
| </td> |
| <td>For conversation about <a href="/docs/glossary.md#fidl">FIDL</a>. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/graphics-dev">graphics-dev</a> |
| </td> |
| <td>For conversation about graphics on Fuchsia. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/intl-dev">intl-dev</a> |
| </td> |
| <td>For conversation about internationalization and localization on Fuchsia. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/media-dev">media-dev</a> |
| </td> |
| <td>For conversation about media and playback on Fuchsia. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/pkg-dev">pkg-dev</a> |
| </td> |
| <td>For conversation about <a href="/docs/glossary.md#fuchsia-package">Fuchsia Packages</a>. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/process-runtime-dev">process-runtime-dev</a> |
| </td> |
| <td>Working group for low-level runtime work shared between the <a href="/docs/glossary.md#zircon">Zircon</a>, Core Platform, and Toolchain teams. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/sdk-dev">sdk-dev</a> |
| </td> |
| <td>For conversation about the <a href="/docs/glossary.md#fuchsia-idk">Fuchsia Integrator Development Kit (IDK)</a>, formerly called the Fuchsia SDK. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/security-dev">security-dev</a> |
| </td> |
| <td>For conversation about Fuchsia’s security architecture. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/session-framework-dev">session-framework-dev</a> |
| </td> |
| <td>For conversation about <a href="/docs/glossary.md#session-framework">Session Framework</a>. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/storage-dev">storage-dev</a> |
| </td> |
| <td>For conversation about filesystems and other storage concerns on Fuchsia. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/toolchain-dev">toolchain-dev</a> |
| </td> |
| <td>For conversation about Fuchsia’s C/C++, Go, and Rust toolchain support. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/rust-users">rust-users</a> |
| </td> |
| <td>Discussion list specifically for Rust toolchain support in Fuchsia. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/ui-input-dev">ui-input-dev</a> |
| </td> |
| <td>Discussion list for those working on user input events. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/zircon-dev">zircon-dev</a> |
| </td> |
| <td>For conversation about <a href="/docs/glossary.md#zircon">Zircon</a>. |
| </td> |
| </tr> |
| </table> |
| |
| ### Platform governance and management |
| |
| The following mailing lists are discussion channels for communicating with |
| Fuchsia’s leadership: |
| |
| <table> |
| <tr> |
| <td><strong>Mailing list</strong> |
| </td> |
| <td><strong>Purpose</strong> |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/api-council">api-council</a> |
| </td> |
| <td>Discussion list for communicating with the <a href="/docs/contribute/governance/api_council.md">Fuchsia API Council</a>. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/community-managers">community-managers</a> |
| </td> |
| <td>Inbound-only discussion list for contacting Fuchsia’s Community Managers with concerns or questions. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/eng-council">eng-council</a> |
| </td> |
| <td>Discussion list for communicating with the Fuchsia <a href="/docs/contribute/governance/eng_council.md">Eng Council</a> about review requests, <a href="/docs/contribute/governance/rfcs.md">RFC</a> feedback, or RFC escalations. |
| </td> |
| </tr> |
| <tr> |
| <td><a href="https://groups.google.com/a/fuchsia.dev/g/eng-council-discuss">eng-council-discuss</a> |
| </td> |
| <td>Discussion list for communicating with the Fuchsia <a href="/docs/contribute/governance/eng_council.md">Eng Council</a>. |
| </td> |
| </tr> |
| </table> |
| |
| ## 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](/docs/development/source_code/contribute_changes.md). |
| |
| |
| ## 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](/docs/contribute/report-issue.md). |