The Rust Team
The Rust project is governed by a number of teams, each focused on a specific area of concern. Below are the rosters, in alphabetical order.
To contact a team, post your question or comment to the Internals forum and tag your post with the category corresponding to the team name. Note that security disclosures should follow the Rust security disclosure process.
Core team
Responsibility: overall direction of the project, subteam leadership, cross-cutting concerns
Language design team
Responsibility: designing new language features
Library team
Responsibility: the Rust standard library, rust-lang crates, conventions
Compiler team
Responsibility: compiler internals, optimizations
Tooling and infrastructure
Responsibility: tool support (e.g. Cargo, rustup), CI infrastructure, etc.
Community team
Responsibility: coordinating events, outreach, commercial users, teaching materials, and exposureContact: community-team [at] rust-lang [dot] org
-
Brian Andersonirc: brson
-
Florian Gilcherirc: skade
-
Manish Goregaokarirc: Manishearth
-
Johann Hofmannirc: johannhof
-
Steve Klabnikirc: steveklabnik
-
Carol Nicholsirc: carols10cents
-
Jan-Erik Redigerirc: badboy
-
Mark Sta Anairc: booyaa
-
Ben Striegelirc: bstrie
-
Erick Tryzelaarirc: erickt
-
Jonathan Turnerirc: jonathandturner
-
Emily Dunhamirc: edunham
Documentation team
Responsibility: ensuring Rust has fantastic documentation
Moderation team
Responsibility: helping uphold the code of conductContact: rust-mods [at] rust-lang [dot] org
