You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I notice that this crate hasn't had a release in a while, and also that there's just one maintaner.
It's normally a good idea to have multiple owners of a crate on crates.io. That way if for any reason you can't work on the project, your co-maintainer can do so (or, further delegate to someone who actually wants to do the work).
Can I respectfully request that you consider appointing a co-maintainer? They don't have to be someone who's willing to do a lot of technical work. They ideally would be someone you'd trust to steward the crate into new ownership, and/or to do the release work after others have prepared the codebase. So ideally they'd be someone you feel aligned with on philosophical/ideological questions as well as just technical taste.
(Having a co-maintainer on crates.io is much more important than co-ownership of the git repository, because switching to a different crate name is very disruptive for downstreams.)
Thanks for your attention.
The text was updated successfully, but these errors were encountered:
Hi.
I notice that this crate hasn't had a release in a while, and also that there's just one maintaner.
It's normally a good idea to have multiple owners of a crate on crates.io. That way if for any reason you can't work on the project, your co-maintainer can do so (or, further delegate to someone who actually wants to do the work).
Can I respectfully request that you consider appointing a co-maintainer? They don't have to be someone who's willing to do a lot of technical work. They ideally would be someone you'd trust to steward the crate into new ownership, and/or to do the release work after others have prepared the codebase. So ideally they'd be someone you feel aligned with on philosophical/ideological questions as well as just technical taste.
(Having a co-maintainer on crates.io is much more important than co-ownership of the git repository, because switching to a different crate name is very disruptive for downstreams.)
Thanks for your attention.
The text was updated successfully, but these errors were encountered: