-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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 Cheng Zhao (@zcbenz) as a collaborator #51479
Comments
Congrats! Welcome to Node.js project, @zcbenz. @nodejs/tsc The deadline have passed. Can an available person schedule an onboarding session with Cheng? |
ping @nodejs/tsc |
Where are you based @zcbenz? If EU working ours would work for you, I can schedule one. |
Thanks for taking this! My timezone is JST, any time between 18:30 and 22:00 JST should work for me next week, you can send an invitation to zcbenz @ gmail.com if there is a time working for you. |
Invite sent for Tuesday. If there are other TSC members or collaborators that want to tag along, lmk. |
FYI you may not be able to check that they can start a CI as it may still be locked down for the upcoming security release. |
Ah true. I'll move to the following week then. |
Fixes: nodejs#51479 PR-URL: nodejs#51812 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com>
I'd like to nominate Cheng Zhao (@zcbenz) as a Node.js collaborator. I'm quite shocked to learn that they're not a collaborator. The contributions speak for themselves.
Commits authored on nodejs/node: https://github.com/search?q=repo%3Anodejs%2Fnode+author%3Azcbenz&type=commits
Pull requests opened: https://github.com/search?q=repo%3Anodejs%2Fnode+author%3Azcbenz&type=pullrequests
Issues opened: https://github.com/search?q=repo%3Anodejs%2Fnode+author%3Azcbenz&type=issues
Comments on pull requests and issues throughout the Node.js organization: https://github.com/search?q=org%3Anodejs+commenter%3Azcbenz&type=pullrequests
cc @nodejs/collaborators
The text was updated successfully, but these errors were encountered: