El equipo de Rust
El proyecto Rust está gobernado por varios equipos, cada uno enfocado en una área de interés especifica. Aquí se encuentran listados en orden alfabético.
Para contactar a un equipo, publica tu pregunta o comentario en el foro interno and tag your post with the category correspondiente a el nombre de cada equipo. Por favor notar que las cuestiones de seguridad deberían regirse al proceso de revelación de seguridad de Rust.
Core team
Responsabilidad: overall direction of the project, subteam leadership, cross-cutting concernsLanguage team
Responsabilidad: designing new language featuresLanguage team shepherds
Responsabilidad: helping guide language RFCs to completion, assisting the language team with its workLibrary team
Responsabilidad: the Rust standard library, rust-lang crates, conventions, and ecosystem supportCompiler team
Responsabilidad: compiler internals, optimizationsDev tools team
Responsabilidad: Rust developer toolsCargo team
Responsabilidad: design and implementation of CargoIDEs and editors team
Responsabilidad: IDEs, editors, and supporting tools such as Racer and the RLSInfrastructure team
Responsabilidad: infrastructure supporting the Rust project itself: CI, releases, bots, metricsContacto: infra@rust-lang.org
Crates.io team
Responsabilidad: management of operations, development, and policies for crates.ioContacto: help@crates.io
Release team
Responsabilidad: tracking regressions, stabilizations, and producing Rust releasesContacto: 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
Responsabilidad: coordinating events, outreach, commercial users, teaching materials, and exposureContacto: 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
Responsabilidad: ensuring Rust has fantastic documentationDocumentation peers
Responsabilidad: oversight of specific documentation, and coordination with the docs teamRustdoc team
Responsabilidad: Documentation tools including Rustdoc and docs.rsModeration team
Responsabilidad: helping uphold the code of conductContacto: rust-mods@rust-lang.org
Rust team alumni
Responsabilidad: 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