New maintainers for wasm-bindgen-rayon?

[pr1metine]

Hi @RReverser,
its safe to say that this project is extremely useful to all of us WebAssembly / Rust devs. Thank you for this ♥.

However, I could not help but notice that you do not respond to recently created issues and PRs. Of course, you are probably busy with other projects. Therefore, I would like to suggest onboarding new maintainers for this project. While I, myself, do not see myself as a suitable maintainer, I am sure that some contributers would be ready to take on this role.

[RReverser]

Hm, I don't think there were many pressing issues.

The most relevant that comes to mind is #10 (comment) which I indeed missed previously, but now it's waiting for the PR author to respond.

I guess I can now merge #12 instead.

[RReverser]

But yeah, if there are willing users, I don't mind sharing the maintainer rights, as long as they're trustworthy (wouldn't want to turn this into a supply chain vector).

[9SMTM6]

I'd be willing to give it a shot. I'd say I'm fairly experienced now with Rust on wasm, and I also know enough about basic web dev (JS etc). That said, I don't use a lot of rayon nor specifically wasm-bindgen-rayon.

I don't have experience maintaining a popular crate, and I don't know how I can prove my trustworthyness. I've merged a few PRs into wgpu, egui, trunk-rs etc, but it was small stuff, documentation and examples.

I think I should at the very least be able to serve as a first responder and merge small PRs such as #13, or ask for some additional required information on issues etc.

[RReverser]

Well, I finally found out why I was missing so many issues and PRs - because this repo was moved over from GoogleChromeLabs org to my personal account, it seems it didn't have "Watch" notifications enabled unless personally pinged 🤦‍♂️

I fixed that now, and should hopefully be able to respond to issues a bit quicker.

[RReverser]

I'll close this for now, let's see how it goes.