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
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.
The text was updated successfully, but these errors were encountered:
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).
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.
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.
The text was updated successfully, but these errors were encountered: