Rust funds a full-time Cargo maintainer after the team lost capacity
Victoria Shinder2 min readThe Rust Project has opened a new full-time Maintainer in Residence position for the Cargo team and filled it with Scott Schafer (@muscraft). The announcement, dated 22 September 2026, is by Jakub Beránek on behalf of the Funding team.
The money comes from the Rust Foundation Maintainers Fund, topped up by the Rust Leadership Council from its Project Priorities budget and by AWS. The position runs for at least twelve months.
The reasoning is unusually candid. Cargo is cross-cutting — it has to support many use cases and integrate with several other tools — and the team "has sometimes struggled with meeting its maintenance demands". The post recalls that Cargo held a feature freeze for several years to reduce internal tech debt, work through the backlog and build scalable internal processes. Then, recently, "some members of the team left, while others lost their dedicated funding for working on Cargo maintenance and had to scale down their involvement."
Schafer joined the Cargo team three years ago and leads the Rust Docker team. He implemented Cargo's workspace inheritance, and drove a multi-year effort to move the compiler's diagnostics rendering onto the annotate-snippets crate — completed in Rust 1.93.0, which let the compiler and Cargo share one diagnostics interface and unblocked the Cargo linting system, now stabilised and shipping in Rust 1.100.0.
The Funding team is explicit that this does not fix the problem: "a single full-time maintainer will not completely solve the maintenance struggles of the Cargo team".
What it means
The sentence worth extracting is the one about people who "lost their dedicated funding... and had to scale down". That describes maintenance capacity as something that can be withdrawn by parties who are not the project, and it is the actual risk model for a build tool that every Rust user runs on every build.
The diagnostics work is the better illustration of what funded time buys. Moving the compiler onto annotate-snippets took years, produced no user-visible feature at the time, and is the reason Cargo linting could be built at all. That is the shape of work volunteers defer indefinitely: high cost, no demo, unblocks someone else later.
Worth noting for anyone reading this as a funding model rather than a news item: the position is twelve months, and the fund is donation-dependent. A maintainer in residence is a lease on capacity, not an acquisition of it.