Nominating @panva to the TSC

[RafaelGSS]

Hello folks!

As I previously shared on the TSC channel, I would like to nominate Filip Skokan (@panva) for the Node.js TSC. Filip has been doing amazing work on Node.js crypto (including participation in the last security release) and other modules, as you can see in his commit history.

He has demonstrated an excellent contributor to collaborate with. I'm sure he will be a great addition to the team.

Commits authored on nodejs/node: https://github.com/nodejs/node/commits?author=panva
Pull requests opened: https://github.com/search?q=author:panva+org:nodejs&type=pullrequests
Issues opened: https://github.com/search?q=author:panva+org:nodejs&type=issues
Comments on pull requests and issues throughout the Node.js organization: https://github.com/search?q=commenter%3Apanva+org%3Anodejs&type=pullrequests

cc: @nodejs/tsc

[tniessen]

+1. I have full confidence in Filip's decision making and he's been a great person to work with for many years.

[anonrig]

+1 I have worked with @panva on multiple occasions, and I have no doubt he'll bring a lot of expertise and experience to the Node.js organization.

[RaisinTen]

+1! Looking forward to having you on the TSC, Filip.

[panva]

Thank you for the nomination and the positive reception so far. ❤️

[ShogunPanda]

+1! Can't wait for this to happen!

[mhdawson]

+1 from me as well

[jasnell]

+1

[RafaelGSS]

No objections, the nomination has passed. I'll update this issue with the onboarding checklist.

[mcollina]

It would be good if @panva showed up to 1+ meetings, but not an hard requirement.

[benjamingr]

+1

[panva]

It would be good if @panva showed up to 1+ meetings, but not an hard requirement.

I'll be joining on Wednesday assuming i get the meeting access credentials by then.

[RafaelGSS]

I'm proceeding with the nomination, then.

• Confirm that the new member has read, understands, and agrees to uphold the
  Code of Conduct.
• Add the new member to the @nodejs/tsc and @nodejs/security-tsc teams.
• Change the new member's role in the GitHub nodejs organization to Owner.
• Add them to the @nodejs-private org and with an Owner role.
• Add them to the @nodejs-private/security-tsc team.
• Add them to the @pkgjs org and with an Owner role.
• Add them to the @pkgjs/node-tsc team.
• Invite them to the HackerOne Node.js team.
  Have them turn on two-factor authentication after they have joined.
• Add them to the tsc mailing list: https://github.com/nodejs/email/edit/main/iojs.org/aliases.json add panva to TSC mailing list email#273
• Add them to the nodejs-tsc Google Group as owners, so they receive Calendar invites for TSC meetings.
• Update the @nodejs/node repository README to reflect membership in the TSC. doc: add Filip Skokan to TSC node#58499
• Update https://github.com/nodejs/create-node-meeting-artifacts/blob/main/templates/invited_tsc to reflect membership in the TSC. update: add panva to voting members create-node-meeting-artifacts#178
• Inform them of the TSC meeting password.
• Ask them what is their handle on OpenJS Slack – and ask them to create one if they haven't one already. Add that handle to the #nodejs-tsc channel.