Maintainers wanted

[alsuren]

I would like to step down from maintaining this project.

I am no longer using rust day to day, so I don't find myself installing rust tools day to day. I've mostly left this thing on autopilot for the last year or so, with minor bursts of activity every few months.

I'm also stopping development on cargo-quickbuild, but that doesn't matter as much because it hasn't got any users.

I have already given merge access to @NobodyXu but I would also like to hand over full ownership of the repo and the crates.io package.

@NobodyXu - if you are interested, please reply with your crates.io username so I can transfer things across.

If there is anyone else who uses cargo-quickinstall regularly and would like to help take over maintenance, please reply to this issue and we can work something out.

I will also add @rust-bus as maintainers.

Is there anything else I should be doing?

[NobodyXu]

@NobodyXu - if you are interested, please reply with your crates.io username so I can transfer things across.

My crates.io username is NobodyXu and email is [email protected]

[NobodyXu]

Is there anything else I should be doing?

I remember that there's also a server that collects the stats (installation report) and update some files on github?

[alsuren]

I remember that there's also a server that collects the stats (installation report) and update some files on github?

Ah yes. That's going to be fun.

I have invited you to the the https://github.com/alsuren/warehouse-clerk-tmp repo on github. You can ignore most files (they're from the template project). Just git log --stat to see which files are actually interesting.

In practice, this piece is optional and mostly takes care of itself.

• cargo-quickinstall and cargo-binstall both send an http request to the stats server on each install attempt
• stats server increments a counter for the appropriate package in redis
• our github actions hourly cronjob fetches the day's requested stats (get-stats.sh) and concatenates that with the list of popular packages when deciding what needs to be built.

https://vercel.com/docs/concepts/projects/overview#transferring-a-project seems a bit involved. I think I will need to create a "Pro Team" to transfer the project to, and then from there it can be transferred to a hobby account again. Until this happens, you will be able to push to main (which automatically triggers deploys) but you won't be able to see the logs if anything goes wrong.

It looks like there are a few chores to do while we're here though (including migrating from nodejs 12 to nodejs 16 or 18). I can do that before handing over if you want.

In theory we could have two stats servers running in parallel and make releases of quickinstall and binstall to divert traffic across gradually. This would also allow us to pick a more sensible-sounding URL in the process.

I would also like to hand over full ownership of the repo and the crates.io package.

I think that if I transfer ownership of this repo directly to another person then all of the urls will change, but we won't be in any better position than we were before (still a bus-factor of 1). I think it might be better for me to transfer everything to the cargo-quick org and then hand over control of the org. I wrote some notes about how to do this over at https://github.com/alsuren/cargo-quickinstall/issues/58.

This is starting to feel like a Christmas project.

I have the 24th of December to the 2nd of January off work (Europe/London timezone), so I will try to do #58 then. We should probably pick a date to coordinate the vercel transfer dance if we decide to do it. I suspect that we can do it all by communicating in public, but can also use email ([email protected]) or discord (alsuren#9966) for more private/real-time communication if we want.

If this is sounding like too much hassle, you can pull out at any time.

[NobodyXu]

It looks like there are a few chores to do while we're here though (including migrating from nodejs 12 to nodejs 16 or 18). I can do that before handing over if you want.

Thanks, that will be great.

In theory we could have two stats servers running in parallel and make releases of quickinstall and binstall to divert traffic across gradually. This would also allow us to pick a more sensible-sounding URL in the process.

I don't think that is a big problem, but I would like to fix #84 .

TBH though, fixing #84 would take quite some effort.

I think that if I transfer ownership of this repo directly to another person then all of the urls will change, but we won't be in any better position than we were before (still a bus-factor of 1). I think it might be better for me to transfer everything to the cargo-quick org and then hand over control of the org. I wrote some notes about how to do this over at #58.

Another option will be transfer the project to cargo-bins, where we have three people there.

We should probably pick a date to coordinate the vercel transfer dance if we decide to do it. I suspect that we can do it all by communicating in public, but can also use email ([email protected]) or discord (alsuren#9966) for more private/real-time communication if we want.

My email is [email protected] , feel free to email me.

If this is sounding like too much hassle, you can pull out at any time.

Not at all and I would like to thank you for this awesome project!

[NobodyXu]

~~@alsuren P.S. are you interested in joining cargo-bins? That would reduce the bus factor for both binstall and quickinstall and unify our effort.~~

Excuse me for this silly message since you mentioned in this issue you no longer use rust frequently.

[alsuren]

Moving quickinstall into cargo-bins org might be the right answer actually. Feel free to add me and I will do the transfer over the Christmas break (I think there may be devops work to do once it is moved, and/or I might need to transfer it back if everything goes pear shaped, so it would be useful for me to be a member even if I later step down)

[NobodyXu]

That's good to hear!

@passcod Can you invite @alsuren to the org cargo-bins please?

[passcod]

Done, sorry for the delay.

[rakshith-ravi]

We (at Patr) use rust heavily and would LOVE to help you out with this project. While we may not have the bandwidth to help maintain this project, we can most definitely help with server resources and hosting for building the packages, as well as hosting the backend. Please do let me know if we can have the opportunity to help out. We would love to! ❤️

[Milo123459]

Could I please join as a maintainer? I'd love to help out with this.

[NobodyXu]

Definitely! I think we need to first invite you to cargo-bins org @passcod