-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
Nominating Claudio Wunder (@ovflowd) to be a collaborator #47672
Comments
@nodejs/collaborators @ovflowd |
Big +1. |
Thank you for the nomination @Trott. I appreciate the gesture by a mile. It's been a fun ride so far with the Node.js project, and I'm super excited about the projects we've been working on. Hopefully, I'm eventually able to make an impact. And I wish to keep learning from this fantastic community. I wanted to thank you, especially @Trott, @bnb, @mhdawson, @joesepi and all the other people supporting me and guiding me through this journey. (Not to mention all the people I had a chance to collaborate with). Thank you! |
Big +1 from me as well. I think you are already making an impact :) |
This has been open for more than a week, so the nomination has passed. Congrats Claudio! 🎉 @nodejs/tsc we need to schedule an onboarding session for @ovflowd. I think I'll be able to help out this weekend. Please let us know if anyone else would also like to join or if anyone else can do the onboarding before the weekend. |
I'd bea able to do the onboarding with him Thursday at 2 or 4 pm ET if that works. |
@Trott was able to give me the onboarding today! |
@ovflowd might be a good chance to ask you (again?) to consider self nominating for moderation? There are areas (for example the website) where there aren't a lot (any?) moderators active and the current process is a back-and-forth through the moderation repo for every spam comment. |
PR-URL: nodejs#47844 Fixes: nodejs#47672 Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Rich Trott <rtrott@gmail.com>
Claudio has been doing extraordinary work on getting the website redesign onto the current website, updating the website stack, and improving the maintainability of our API docs tooling and processes. It will ease their work to have better access and the ability to review API doc changes and tooling changes that will affect the website. Their actual commits authored in the core repo are few at this point, but the amount of planning and consultation they've had to do is more impactful than many folks with more commits. In the near future, he will be writing new workflows for the CI and things related to nodejs/next-10#166.
At this point, there can be little doubt about their diligence and commitment.
https://github.com/orgs/nodejs/teams/collaborators
The text was updated successfully, but these errors were encountered: