Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New maintainers for wasm-bindgen-rayon? #14

Open
pr1metine opened this issue Oct 1, 2024 · 3 comments
Open

New maintainers for wasm-bindgen-rayon? #14

pr1metine opened this issue Oct 1, 2024 · 3 comments

Comments

@pr1metine
Copy link

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
Copy link
Owner

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
Copy link
Owner

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
Copy link
Contributor

9SMTM6 commented Oct 3, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants