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 concernsLanguage team
Responsibility: designing new language featuresLanguage team shepherds
Responsibility: helping guide language RFCs to completion, assisting the language team with its workLibrary team
Responsibility: the Rust standard library, rust-lang crates, conventions, and ecosystem supportCompiler team
Responsibility: compiler internals, optimizationsDev tools team
Responsibility: Rust developer toolsCargo team
Responsibility: design and implementation of CargoIDEs and editors team
Responsibility: IDEs, editors, and supporting tools such as Racer and the RLSInfrastructure team
Responsibility: infrastructure supporting the Rust project itself: CI, releases, bots, metricsContact: infra@rust-lang.org
Crates.io team
Responsibility: management of operations, development, and policies for crates.ioContact: help@crates.io
Release team
Responsibility: tracking regressions, stabilizations, and producing Rust releasesContact: release@rust-lang.org
-
Mark Rousskovirc: simulacrum
-
Joe Roznerirc: jrozner
-
Joseph Kordishirc: jkordish
-
Josh Stoneirc: cuviper
-
Alex Crichtonirc: acrichto
-
Sertac Olgunsoyluirc: dirtybit
-
Mazdak Farrokhzadirc: centril
-
Sean Griffinirc: sgrif
-
Pietro Albiniirc: pietroalbini
-
BatmanAoDirc: BatmanAoD
-
Pramod Bishtirc: PramodBisht
-
Lubitsirc: Lubits
-
Araz Abishovirc: ArazAbishov
-
Aaron Powerirc: Aaronepower
-
Trevor Reiffirc: treiff
-
cssivisionirc: cssivision
-
Giovanni Sollazzoirc: gsollazzo
-
pambihirairc: pambihira
-
Stokhosirc: stokhos
Community team
Responsibility: coordinating events, outreach, commercial users, teaching materials, and exposureContact: community@rust-lang.org
-
Florian Gilcherirc: skade
-
Manish Goregaokarirc: Manishearth
-
Sebastián Magríirc: sebasmagri
-
Jan-Erik Redigerirc: badboy
-
Mark Sta Anairc: booyaa
-
Ashley Williamsirc: agdubs
-
Olivia Huggerirc: liv
-
Josh Gouldirc: technetos
-
Arshia Muftiirc: arshia
-
Parry Wilcoxirc: parrywinkle
-
Katharinairc: spacekookie
-
István Szmozsánszkyirc: flaki
-
Matt Gathuirc: mattgathu
-
Claus Matzingerirc: celaus
-
Wesley Mooreirc: wezm
-
Ben Striegelirc: bstrie
-
Jonathan Turnerirc: jntrnr
Documentation team
Responsibility: ensuring Rust has fantastic documentationDocumentation peers
Responsibility: oversight of specific documentation, and coordination with the docs teamRustdoc team
Responsibility: Documentation tools including Rustdoc and docs.rsModeration team
Responsibility: helping uphold the code of conductContact: rust-mods@rust-lang.org
Rust team alumni
Responsibility: enjoying a leisurely retirement-
James Millerirc: aatch
-
Alexis Beingessnerirc: Gankroteams: libs
-
Patrick Waltonirc: pcwalton
-
Huon Wilsonirc: huonteams: core, lang, libs
-
Jeremiah Peschkairc: peschkaj
-
Björn Steinbrinkirc: doenerteams: compiler
-
Brian Koropoffirc: bkoropoffteams: compiler
-
Brian Andersonirc: brson
-
Erick Tryzelaarirc: erickt
-
Ariel Ben-Yehudairc: arielb1
-
Jeffrey Seyfriedirc: jseyfried
-
E. Dunhamirc: edunham
-
Tom Princeirc: tomprince