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 team

Responsibility: designing new language features

Language team shepherds

Responsibility: helping guide language RFCs to completion, assisting the language team with its work

Library team

Responsibility: the Rust standard library, rust-lang crates, conventions, and ecosystem support

Library team shepherds

Responsibility: coordinating the Libz Blitz, helping guide libs RFCs to completion, keeping pulse on the ecosystem

Compiler team

Responsibility: compiler internals, optimizations

Dev tools team

Responsibility: overall direction for tools for working with Rust code

Dev tools peers

Responsibility: oversight of specific Rust tools, and coordination with dev tools team

Cargo team

Responsibility: design and implementation of Cargo

Infrastructure team

Responsibility: infrastructure supporting the Rust project itself: CI, releases, bots, metrics
Contact: infra-team@rust-lang.org

Community team

Responsibility: coordinating events, outreach, commercial users, teaching materials, and exposure
Contact: community-team@rust-lang.org

Documentation team

Responsibility: ensuring Rust has fantastic documentation

Moderation team

Responsibility: helping uphold the code of conduct
Contact: rust-mods@rust-lang.org

Style team

Responsibility: temporary 'strike team' charged with deciding on code style guidelines and configuring Rustfmt (process specified in RFC 1607)
Contact: style-team@rust-lang.org

Rust team alumni

Responsibility: enjoying a leisurely retirement