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 teamResponsibility: overall direction of the project, subteam leadership, cross-cutting concerns
Language design teamResponsibility: designing new language features
Library teamResponsibility: the Rust standard library, rust-lang crates, conventions
Compiler teamResponsibility: compiler internals, optimizations
Tooling and infrastructureResponsibility: tool support (e.g. Cargo, rustup), CI infrastructure, etc.
Community teamResponsibility: coordinating events, outreach, commercial users, teaching materials, and exposure
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: jntrnr
E. Dunhamirc: edunham
Documentation teamResponsibility: ensuring Rust has fantastic documentation
Moderation teamResponsibility: helping uphold the code of conduct
Style teamResponsibility: temporary 'strike team' charged with deciding on code style guidelines and configuring Rustfmt (process specified in RFC 1607)