--- title: "Ownership in Rust · baby steps" url: https://daily.dev/posts/ownership-in-rust-baby-steps-efqup6hwz source_url: https://smallcultfollowing.com/babysteps/blog/2024/04/05/ownership-in-rust type: article source: "Niko Matsakis - baby steps" published: 2026-05-31T07:54:20.803Z updated: 2026-05-31T09:20:11.260Z tags: ["open-source", "rust", "project-management"] reading_time: 7 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Ownership in Rust · baby steps **[Niko Matsakis - baby steps](https://daily.dev/sources/babysteps)** · 7 min read · 0 upvotes · 0 comments ## Summary 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. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: --- Tags: [#open-source](https://daily.dev/tags/open-source), [#rust](https://daily.dev/tags/rust), [#project-management](https://daily.dev/tags/project-management) [View this post on daily.dev](https://daily.dev/posts/ownership-in-rust-baby-steps-efqup6hwz)