Why Did Rust’s Core Review Team Resign? Inside the Open‑Source Governance Crisis

Open‑Source Governance Crisis After Rust Review Team Resignation

On the morning of November 22, the Rust programming language’s review team announced a collective resignation that took effect immediately via a GitHub pull request, which is now locked.

The announcement quickly ignited heated discussion among developers worldwide and the broader open‑source community.

Team member Andrew Gallant wrote that the resignation was “in protest of the Core Team placing themselves unaccountable to anyone but themselves.”

The review team, responsible for maintaining the code of conduct and community standards, felt the core team had exceeded its authority.

Gallant outlined four concrete recommendations for moving forward:

Establish shared responsibility for overseeing the core team, rather than the core team being accountable only to itself.

Replace the review team with members drawn from the broader Rust team instead of core‑team members.

Allow the future team, guided by Rust team members, to proactively address unhealthy conflicts and consider professional mediation.

Pay special attention to maintaining a healthy size and diversity within the team.

Rust has already appointed a temporary group, naming Khionu Sybiern and Joshua Gould as new members, with Gould already part of the Rust community team.

The former team members were thanked for their contributions, and they expressed willingness to contact Rust team members for advice or clarification.

Rust’s Popularity: Ideals vs. Reality

Since 2016, Stack Overflow’s developer survey has repeatedly voted Rust as the most loved programming language through 2021.

The Rust community follows the “Rustacean Principles,” which emphasize reliability, performance, support, productivity, transparency, and versatility.

Reliability: If it compiles, it works.

Performance: Idiomatic code runs efficiently.

Support: Language, tools, and community provide help.

Productivity: Small effort yields large results.

Transparency: You can predict and control low‑level details.

Versatility: You can use Rust for anything.

Leaders such as Niko Matsakis, Shane Miller, and other key members are working to ensure Rust’s long‑term popularity, which is expected to continue into 2022 and beyond.

The recent governance dispute shows that when ideals meet harsh reality, teamwork becomes crucial, and internal conflicts can become costly setbacks for technical teams.