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 2021 RoadmapTeams
Core team
Managing the overall direction of Rust, subteam leadership, and any cross-cutting issues
Members & ContactsCommunity team
Coordinating and supporting events, content creation, and the RustBridge program, as well as conducting community surveys
Members & ContactsCrates.io team
Managing operations, development, and official policies for crates.io
Members & ContactsInfrastructure team
Managing the infrastructure supporting the Rust project itself, including CI, releases, bots, and metrics
Members & ContactsLibrary team
Managing and maintaining the Rust standard library and official rust-lang crates
Members & ContactsRelease team
Tracking regressions and stabilizations, and producing Rust releases
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 improving 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 & ContactsRust by Example working group
Maintaining and updating the official Rust by Example book
Members & ContactsWebAssembly (WASM) working group
Improving on the end-to-end experience of embedding Rust code in JS libraries and apps via WebAssembly
Members & Contacts