Rust Announces New Leadership Council and Governance Model

Rust Announces New Leadership Council and Governance Model

Earlier this month we published "Rust Internal Chaos Never Ends," which described internal turmoil and political fights within the Rust team, raising concerns that the ongoing disorder could damage the language’s reputation and development.

The Rust team, feeling the crisis and the shortcomings of the current governance, announced a major restructuring of its organization.

The project has established a new top‑level governance body: the Rust Leadership Council. This council replaces the previously chaotic core team and temporary leadership positions, with responsibilities now handled by Rust directors.

Background Summary

Rust originated at Mozilla and evolved there for many years; its early governance structure also derived from Mozilla. Around 2017, Rust created roughly six teams—core, language, mod, library, and cargo. The core team primarily supervised issues across other Rust teams.

As the language and community grew, the core team’s authority expanded, giving it the highest decision‑making power over Rust’s direction, while other teams could not influence it. We previously reported on the Rust moderation team’s collective resignation in protest of the core team, noting that the core team did not follow the same Code of Conduct (CoC) and that CoC became a tool for the core team to enforce rules, even being weaponized by a core team member against male contributors.

Moreover, the core team’s responsibilities became overly numerous and messy. Because the core team both identified problems and had to solve them without oversight, it acted as both referee and participant, leading to overload.

In summary, the old governance model was vague and its coarse power division contributed to the current crisis.

New Governance Model

After multiple governance crises, Rust teams collaboratively drafted an RFC titled "Rust Leadership Council" to reshape leadership and governance.

The draft establishes the removal of the Rust core team and the creation of a top‑level governance team, the Leadership Council, composed of representatives from each team.

The Leadership Council will not perform hands‑on work itself; instead, it will handle ambiguous work assignments and priorities, delegating tasks to sub‑teams or individual members with precise responsibility.

Additionally, the Council aims to coordinate cross‑team work, planning, and long‑term project success, acting as a coordination, organization, and accountability body. It will manage changes caused by projects, ensure top‑level teams take responsibility, and represent the official stance of the Rust project.

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

The majority of Rust’s development and maintenance work—such as compiler and core tool upkeep, language and standard library evolution, and infrastructure management—remains the responsibility of nine top‑level teams.

The first Rust Leadership Council consists of representatives from these nine 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

The core team has been dissolved; its members have either left voluntarily or been removed. In the coming weeks, the Rust team will focus on building basic infrastructure for the new Leadership Council, including regular meeting schedules, agenda processes, repository setup, and transitioning from the previous leadership structure.

Ultimately, the community’s current “chaotic and unordered” state stems largely from this governance model.

Unlike Python and Linux, Rust never had a single figure with high technical authority, influence, and charisma to guide the project.

Guido van Rossum, the creator of Python, is famously known as the Benevolent Dictator‑For‑Life (BDFL).

The BDFL title is held by a few open‑source leaders who, as founders, retain final decision‑making power during community disputes.

Linus Torvalds, the creator of Linux, is similarly revered as the “King of Linux.”

<code>长按或扫描下方二维码，免费获取 Python公开课和大佬打包整理的几百G的学习资料，内容包含但不限于Python电子书、教程、项目接单、源码等等</code>

<code>推荐阅读
“让Python快5倍”最新计划：优化解释器和内存管理
Ruff v0.0.281 发布，Rust 编写的高性能 Python 代码分析工具
整理了34个Python自动化办公库
Pycharm 常用快捷键大全，全网最全！</code>

Click Read Original to learn more.