Niko Matsakis explores the concept of 'ownership' in the Rust open source project — not the type system, but organizational ownership of goals. Under a proposed project goals system, each priority goal gets a designated owner (ideally one person) who drives design decisions and keeps work moving. Owners don't have final say — teams do — but they are empowered to make calls within their domain. The system is built on mutual trust: owners must be known to the project and demonstrate good judgment, while the project commits to responding and providing support. Accountability is maintained through regular status updates and periodic blog posts aggregating progress. The post also clarifies that Rust's consensus model doesn't require unanimity — teams decide, not RFC threads, and consensus means no one thinks a proposal is definitely wrong, not that everyone agrees.
