Governance
How Rust is built by its community
Roadmap and RFC process
Each major decision in Rust starts as a Request for Comments (RFC). Everyone is invited to discuss the proposal, to work toward a shared understanding of the tradeoffs. Though sometimes arduous, this community deliberation is Rust’s secret sauce for quality.
Learn MoreThe RFC process is also used to establish a yearly roadmap laying out our aspirations for that year. This shared vision is essential for keeping the development process focused.
Read the 2019 RoadmapTeams
Community team
Coordination and supporting events, content creation, running the RustBridge program, and conducting the survey.
Members & ContactsCrates.io team
Management of operations, development, and policies for crates.io.
Members & ContactsLibrary team
the Rust standard library, rust-lang crates, conventions, and ecosystem support
Members & ContactsWorking Groups
Command-line interfaces (CLI) working group
Focusing on the end-to-end experience of writing terminal apps, both large and small, in Rust.
Members & ContactsEmbedded devices working group
Focusing on the end-to-end experience of using Rust in resource-constrained environments and non-traditional platforms.
Members & ContactsGame development working group
Focusing on making Rust the default choice for game development.
Members & ContactsNetworking working group
Focusing on the end-to-end experience for both sync and async networking code, in coordination with the growing ecosystem in this space.
Members & ContactsWebAssembly (WASM) working group
Focusing on the end-to-end experience of embedding Rust code in JS libraries and apps via WebAssembly.
Members & Contacts