Crate ownership, volunteering

[ijackson]

Hi. We use this crate in arti, which is our project to reimplement Tor in Rust. We would like to rely on some of the fixes currently available in merge requests.

I saw your note on the front page, saying you were looking for a new maintainer. Well done for recognising that you need to step back, and for communicating clearly. Thank you.

I would like to volunteer to take over this crate.

Links that might help you check that I'm a real human:
https://crates.io/users/ijackson
https://diziet.dreamwidth.org/
https://gitlab.torproject.org/Diziet

[ijackson]

FTR, the arti MR that prompted me to make this offer was this one: https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/274

[ijackson]

In the absence of a response, and in order to be unblocked, I have forked this crate as shellexpand-fork, and merged the one bugfix that we needed in arti, #13

Right now I'm not promoting this particularly hard but I am considering dropping a note about the fork in the issues and MRs which are open here against the original shellexpand.

[netvl]

Hi @ijackson
I'm sorry, but at this point of time I'm not sure I even can answer tickets here due to my employer's policy.
I will try to resolve that, and then work on transferring the crate to you.

[ijackson]

Hi. Thanks for the reply! That employer policy sounds very strict - good luck with it. I appreciate your efforts.

FTR, the command I would like you to run is

cargo owner --add ijackson shellexpand

(I guess we're going to have to (keep) using my gitlab.com for hosting since this one is in your personal github namespace.)

[hasezoey]

Hi, i would also be volunteering to maintain this project

[ijackson]

OK, thanks @netlvl, I guess you are still having trouble getting employer permission to transfer ownership. One option that occurred to me is that maybe folks at the Rust Foundation would be able to help negotiate with your employer. Possibly your employer is even one of the corporate members. So you might like to try emailing the Foundation.

Sadly, if you aren't even able to transfer ownership of the crate name I think I will have to proceed with the forked name. I will be away next week, but (supposing there's no movement) on my return I will make something of an effort to point people at my fork (eg in the various issues and MRs here, and maybe I will make a blog post).

Thanks, and my sympathies to you for what is obviously a very awkward position.

[netvl]

There were some good news about processes on my side, so I may be able to do something with this soon, within a few weeks. Sorry about all this stuff!

[ijackson]

OK, thanks, and please do keep us informed.

[ijackson]

ping?

[netvl]

Sorry for the silence - the approval process is underway. Unfortunately I can't expedite it. I do hope it will finish soon - I'm pretty sure it will be approved, it's just that the process takes a lot of time :(

[netvl]

@ijackson I'm very sorry it took so long, but just today I got an approval to do this. I can now do the necessary stuff to transfer the repo/crate ownership. Please tell me if you're still interested; otherwise, I'm just going to archive the repo.

[ijackson]

Hi. I am still interested, yes please!

Ideally you would make me cargo owner of the crate name; I guess it might be useful for you to grant me some permissions over this github repository so I can do some gardening or whatever, but obviously we won't be continuing the development here.

[ijackson]

I wrote:

FTR, the command I would like you to run is

cargo owner --add ijackson shellexpand

(repasting this since it's a bit lost ^ up there in the scroll of messages)

[netvl]

Sorry for the silence, got some personal matters to attend to. Will do it asap. Then I'll update the readme and archive the repo.

[netvl]

@ijackson added you as an owner. Could you please give me a link to where the development happens now? I'll add it to the readme.

[ijackson]

Hi. Thank you!

My repository is at https://gitlab.com/ijackson/rust-shellexpand.

[ijackson]

I intend to go through the open MRs and see what to do about them. Possibly, I will merge some; others I hope to invite the contributor to my gitlab. So I would appreciate it if you would defer archiving this repo for a few days while I do that. Thanks!

[netvl]

Thank you! I'll push an update to the readme soon. Plz ping me here once you think it is safe to archive the repo)

[ijackson]

@netvl Thanks. I have put a note into each of the open MRs and issues, and (where I thought it seemed a good idea) opened issues in my own repo. I think you can archive this at your convenience (after your README update, I presume)

Thank you for your help, and best wishes.

Ian.