Rust-teamet

Rust-projektet styrs av flera team som var och en fokuserar på ett specifikt problemområde. Nedan finns laguppställningar i alfabetisk ordning.

För att kontakta ett team, skicka in din fråga eller kommentar på internforumet och märk ditt inskick med kategorin som motsvarar teamets namn. Notera att tillkännagivanden kring säkerhet ska följa rusts säkherhetstillkännagivandeprocess.

Core team

Ansvar: overall direction of the project, subteam leadership, cross-cutting concerns

Language team

Ansvar: designing new language features

Language team shepherds

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

Library team

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

Compiler team

Ansvar: compiler internals, optimizations

Dev tools team

Ansvar: overall direction for tools for working with Rust code

Dev tools peers

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

Cargo team

Ansvar: design and implementation of Cargo

Infrastructure team

Ansvar: infrastructure supporting the Rust project itself: CI, releases, bots, metrics
Kontakt: infra@rust-lang.org

Release team

Ansvar: tracking regressions, stabilizations, and producing Rust releases
Kontakt: release@rust-lang.org

Community team

Ansvar: coordinating events, outreach, commercial users, teaching materials, and exposure
Kontakt: community@rust-lang.org

Documentation team

Ansvar: ensuring Rust has fantastic documentation

Documentation peers

Ansvar: oversight of specific documentation, and coordination with the docs team

Moderation team

Ansvar: helping uphold the code of conduct
Kontakt: rust-mods@rust-lang.org

Style team

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

Rust team alumni

Ansvar: enjoying a leisurely retirement