Rust governance
summary
Describes concrete governance mechanics: teams for Lang, compiler, DevTools, rustfmt, rustup and cargo; the Rust Foundation handling legal/financial support; decision boundaries like Lang team decides language features versus compiler-local choices; community RFC-driven language changes and a core team supports other teams model. Calls out recurring pain points — licensing, trademarks, moderation, cross-team coordination — and three working laws: urgent versus important gaps, transparency difficulty, and diffusion of responsibility.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 4:09Status quo
- 7:56Pros and cons
- 11:20Compiler change
- 15:18Legal requirements
- 16:51Nonurgent issues
- 19:05Who makes the decision
- 20:46What does Rust governance need
- 22:39Failure modes
