Rust Introduces a New Leadership Council and Overhauls Its Governance Model

Earlier this month we published an article titled “Rust Internal Chaos Never Ends,” which highlighted internal turmoil and political disputes within the Rust team, raising concerns that such disorder could harm the language’s reputation and development.

The Rust community has now announced a major restructuring of its organization by establishing a new top‑level governance institution called the Rust Leadership Council.

Background

Rust originated at Mozilla and inherited its early governance structure from there. Around 2017 the project created roughly six teams (core, language, mod, library, cargo, etc.), with the core team primarily overseeing issues across the other teams.

As the language and community grew, the core team’s authority expanded, giving it the highest decision‑making power while other teams had little influence. This led to complaints, including a resignation of the moderation team citing inconsistent application of the Code of Conduct and alleged misuse of authority.

The core team also became overloaded with responsibilities, having to both identify problems and solve them without clear oversight, which contributed to governance crises.

New Governance Model

After multiple governance crises, Rust contributors drafted an RFC proposing a “Rust Leadership Council” to reshape leadership and governance.

The proposal removes the Rust core team and creates a council composed of representatives from each of the nine top‑level teams.

The council will not perform hands‑on work; instead, it will set priorities for ambiguous tasks, delegate work to sub‑teams or individuals, and act as a coordination, organization, and accountability body for cross‑team projects and long‑term success.

This RFC was co‑authored by @jntrnr (core team member), @joshtriplett (language team lead), @khionu (mediation team member), @Mark‑Simulacrum (foundation core project lead), @rylev (foundation core project lead), @technetos (mediation team member) and @yaahc (foundation collaborative project lead).

The majority of Rust’s development and maintenance (compiler, core tools, language, standard library, infrastructure, etc.) remains the responsibility of the nine top‑level teams.

The first Rust Leadership Council consists of representatives from these teams:

Compiler: Eric Holk

Crates.io: Carol (Nichols || Goulding)

Dev Tools: Eric Huss

Infrastructure: Ryan Levick

Language: Jack Huey

Launching Pad (new, not yet formalized): Jonathan Pallant

Library: Mara Bos

Moderation: Khionu Sybiern

Release: Mark Rousskov

With the core team dissolved, the Rust community’s immediate focus is to build the basic infrastructure for the new council, including regular meeting schedules, agenda processes, repository setup, and transitioning from the previous leadership structure.

The article also notes that unlike Python and Linux, Rust never had a single, highly influential figure (such as a BDFL) to guide its development, which contributed to the current governance challenges.