-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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 Raz Luvaton (@rluvaton) for Collaborator #49049
Labels
meta
Issues and PRs related to the general management of the project.
Comments
Thank you! I'm honored! |
benjamingr
added
the
meta
Issues and PRs related to the general management of the project.
label
Aug 7, 2023
@nodejs/tsc can someone schedule an onboarding? I'll do my best to join as an observer A week has passed 🎉 |
@nodejs/tsc one more attempt |
@benjamingr I think both of us can take this onboarding if no other TSC member is available. |
I am available, you may add me to the invite |
Happy to help, if needed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Raz has been contributing to Node.js for a while, recently he has proven himself in terms of patience and understanding of the code. He has been very receptive to feedback in hard to change areas of the code like streams and cancellation and has been happy to close/stop stuff when it didn't reach consensus gracefully.
Pull Requests in Node.js: nodejs/node/issues (author:rluvaton sort:updated-desc)
Commits in Node.js: nodejs/node/commits?author=rluvaton
Comments in Node.js: nodejs/node/issues (commenter:rluvaton sort:updated-desc)
cc @nodejs/collaborators
The text was updated successfully, but these errors were encountered: