Governance
How Rust is built by its community
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.
Teams
Leadership council
Charged with the success of the Rust Project as whole, consisting of representatives from top-level teams
Compiler team
Developing and managing compiler internals and optimizations
crates.io team
Managing operations, development, and official policies for crates.io
Infrastructure team
Managing the infrastructure supporting the Rust project itself, including CI, releases, bots, and metrics
Library team
Managing and maintaining the Rust standard library and official rust-lang crates
Moderation team
Helping uphold the code of conduct and community standards
Working Groups
Async working group
Pursuing core language and library support for async-await
Command-line interfaces (CLI) working group
Focusing on the end-to-end experience of writing terminal apps, both large and small, in Rust.
Embedded devices working group
Focusing on improving the end-to-end experience of using Rust in resource-constrained environments and non-traditional platforms
Game development working group
Focusing on making Rust the default choice for game development
Rust by Example working group
Maintaining and updating the official Rust by Example book
Security Response WG
Triaging and responding to incoming vulnerability reports
Triage working group
Triaging repositories under the rust-lang organisation
WebAssembly (WASM) working group
Improving on the end-to-end experience of embedding Rust code in JS libraries and apps via WebAssembly