Nominating @MoLow to the TSC

[cjihrig]

I would like to nominate @MoLow to the @nodejs/tsc.

Moshe authored Node's watch mode, has made significant contributions to the test runner in core and on npm, and has recently joined the Build WG.

• @MoLow's nomination as a collaborator, which includes many links to his activity around the org.
• I have raised this to the TSC in private and there were no objections.
• I have contacted @MoLow in private and verified interest.

[mhdawson]

+1 from me

[cjihrig]

This has been open for a week with plenty of positive reactions and I have not received any objections publicly or privately. I think we can move forward with this.

[cjihrig]

(Technically this is on the TSC agenda for this week. We did briefly discuss it last week though and we may be cancelling the meeting tomorrow.)

[cjihrig]

Onboarding of voting members

• 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 and crypto-export mailing lists.
• 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.
• Update https://github.com/nodejs/create-node-meeting-artifacts/blob/main/templates/invited_tsc to reflect membership in the TSC.
• 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.