Repository navigation
Nominating Chengzhong Wu (@legendecas) to the TSC #1282
Description
Activity
+1 assuming is up for it :)
I should have mentioned I have talked to Chengzhong and he is interested.
+1
+1
+1
+1
+1 for sure!
+1
+1
+1
By my count we have 14/20 +1s so far and no objections.
I will wait until after the TSC meeting this week and then close the vote (The goverance says
The TSC may add additional members to the TSC by a standard TSC motion and vote.) and the +1's emoji's in this issue will be tallied to get the vote results after the TSC meeting.I'll volunteer to onboard @legendecas assuming the vote is positive. Anybody else want to join us?
Reacted by Chengzhong Wu@legendecas I'll co-ordinate with you for the onboarding separately:
- Confirm that the new member has read, understands, and agrees to uphold the
Code of Conduct. - Add the new member to the
@nodejs/tscand@nodejs/security-tscteams. - Change the new member's role in the GitHub
nodejsorganization toOwner. - Add them to the
@nodejs-privateorg and with anOwnerrole. - Add them to the
@nodejs-private/security-tscteam. - Add them to the
@pkgjsorg and with anOwnerrole. - Add them to the
@pkgjs/node-tscteam. - Invite them to the HackerOne Node.js team.
Have them turn on two-factor authentication after they have joined. - Add them to the
tscandcrypto-exportmailing lists. - Add them to the nodejs-tsc Google Group as owners, so they receive Calendar invites for TSC meetings.
- Update the
@nodejs/noderepository README to reflect membership in the TSC. - Update https://github.com/nodejs/create-node-meeting-artifacts/blob/main/templates/invited_tsc to reflect membership in the TSC.
Reacted by Chengzhong Wu- Confirm that the new member has read, understands, and agrees to uphold the
@legendecas can you confirm:
Confirm that the new member has read, understands, and agrees to uphold the
Code of Conduct.8 remaining items
- added a commit that references this issue
on Sep 16, 2022 I think the only thing left to do is to add @legendecas to HackerOne (and maybe to the Google Group--I didn't check that one).
@mhdawson Let me know if you want me to handle HackerOne or find someone to handle the Google Group. Otherwise, I'll assume you're waiting to talk to @legendecas about something first or something like that.
Ok all done.
Reacted by Tobias Nießen- added 3 commits that reference this issue
on Sep 26, 2022 - added 2 commits that reference this issue
on Jan 3, 2023
I'd like to nominate Chengzhong Wu (@legendecas)[https://github.com/legendecas].
He has contributed over a number of years and has 83 commits to Node.js core, has been involved in 440 issues in node.js core and is a significant contributor to Node-api and the work of the Node-api team. He has also been contributing to diagnostic efforts and is leading the ShadowRealm initiative.
He's been very collaborative, contributes in a thoughtful and respectful way, and works to help move the work of the project forward in a scope greater than individual commits/issues. I've enjoyed my interactions with him and I think he'd be a good addition to the TSC.