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
tl;dr: Please add a crates.io co-owner to improve the bus factor for this crate and dirs-ng.
Hi.
Relevantly, I'm the current maintainer of shellexpand, which I inherited from its author when they weren't able to work on it any more. I was recently asked to swtich from dirs to home.
The principal motivation seems to have been to avoid the MPL. I strongly disagreed; I did some evaluation of both crates and concluded that I would like to stay with dirs.
However, the biggest point against dirs was the single ownership of the crate name on crates.io. I would respectfully request that you add a second crate owner. Single crate ownership can cause serious inconvenience if the owner can't work on the crate for any reason. (Indeed shellexpandhad to be forked for many months and dirs seems to have had a temporary fork too.)
Your co-owner doesn't really have to do anything, other than approve (or not!) volunteers who come forward if you (for any reason) aren't available.
Obviously you'll want to pick someone you feel is ideologically aligned, and has similar engineering taste, and so on. Hopefully you'll have a friend or colleague you can prevail on. For the record: I am volunteering, but I don't want this request to be read as a request for you to grant co-ownership to me. I just want to avoid the risk iof having to rename the crate on crates.io; that would be seriously disruptive for your thousands of dependencies).
Thanks for your attention.
The text was updated successfully, but these errors were encountered:
tl;dr: Please add a crates.io co-owner to improve the bus factor for this crate and dirs-ng.
Hi.
Relevantly, I'm the current maintainer of
shellexpand
, which I inherited from its author when they weren't able to work on it any more. I was recently asked to swtich fromdirs
tohome
.The principal motivation seems to have been to avoid the MPL. I strongly disagreed; I did some evaluation of both crates and concluded that I would like to stay with
dirs
.However, the biggest point against
dirs
was the single ownership of the crate name on crates.io. I would respectfully request that you add a second crate owner. Single crate ownership can cause serious inconvenience if the owner can't work on the crate for any reason. (Indeedshellexpand
had to be forked for many months anddirs
seems to have had a temporary fork too.)Your co-owner doesn't really have to do anything, other than approve (or not!) volunteers who come forward if you (for any reason) aren't available.
Obviously you'll want to pick someone you feel is ideologically aligned, and has similar engineering taste, and so on. Hopefully you'll have a friend or colleague you can prevail on. For the record: I am volunteering, but I don't want this request to be read as a request for you to grant co-ownership to me. I just want to avoid the risk iof having to rename the crate on crates.io; that would be seriously disruptive for your thousands of dependencies).
Thanks for your attention.
The text was updated successfully, but these errors were encountered: