Lots of crates on crates.io have only a single owner. That’s a huge responsibility for the sole owners, and also a risk for crate users. When solo owners disappear (for lots of reasons — life happens) it’s a major problem, because the crate becomes impossible to change: there’s nobody to release a bug fix, and there isn’t even a way to add new maintainers. Users are left with abandoned crate, and forks of these creates, which are soon abandoned too, and so on.
I think it’s best to solve this problem proactively by having a group of volunteers who are happy to be added as backup owners of crates. It’s especially important for new projects that may not have anybody to invite as co-owner yet.
You can add
github:rust-bus:maintainers*) as an owner of your create and:
- We promise not to touch the create as long as its actively maintained. You add
rust-bus-owneronly as a backup to maintain the create in your absence.
- If an urgent bugfix is needed (e.g. compatibility with next version of Rust, or a security issue) and you’re gone for weeks or longer, we may release a patch version with the fix.
- If you’re gone for months, we’ll help find a new maintainer and a new home for it. If there’s an active fork, we’ll help migrating users to the fork. You will always remain as the owner of your crate, in case you choose to continue maintaining it in the future.
Technicalities of adding backup owners:
You can run
cargo owner --add rust-bus-ownerin your create. Anyone can do that for any create.
- If you’re a trusted person within Rust community, let me know your GitHub username and I’ll add you to the GitHub org, and then you will be able to run
cargo owner --add github:rust-bus:maintainers
That oddity is because ideally crates should be managed by teams, but Cargo doesn’t support adding teams by non-team-members (yet, hopefully).