Re-nominate @gireeshpunathil to TSC

[mhdawson]

@gireeshpunathil stepped down from the TSC as IBM was over the maximum numbers after one of the TSC members resigned. As part of that discussion it was suggested we should re-nominate him as soon as the numbers were expanded. I'm formalizing that suggestion in this issue,

Once we confirm @BridgeAR (see #811). I'd like to nominate @gireeshpunathil to rejoin the TSC.

I'd also suggest we can waive the usual 3 weeks of attending the TSC meetings as an observer due to his recent participation in the TSC over the last year.

[Trott]

I'd also suggest we can waive the usual 3 weeks of attending the TSC meetings as an observer due to his recent participation in the TSC over the last year.

Yes, absolutely. That's an informal guideline. I don't think it's documented anywhere. So we can absolutely waive it at our discretion.

[Trott]

I do have a concern that may block this for a few weeks that I will email you (@mhdawson) and @gireeshpunathil about privately. TSC about.

[cjihrig]

+1 to re-adding Gireesh as soon as possible.

[mhdawson]

@Trott thanks for the heads up, even if it is blocked for a bit wanted to get the suggestion formalized and ready to go when it is appropriate.

[tniessen]

+1, as soon as the other issue is resolved

[sam-github]

+1 from me, and thanks again to @gireeshpunathil for graciously stepping down.

[jasnell]

+1

[danbev]

+1

[mcollina]

+1

[joyeecheung]

+1

[danbev]

+1 lör 7 mars 2020 kl. 17:12 skrev Joyee Cheung <[email protected]>:

…

+1 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#829?email_source=notifications&email_token=AADJRX5YH3DBXF3GBDSOYUDRGJW7PA5CNFSM4K5CVKU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOD5FSY#issuecomment-596103883>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADJRX66FLN3AYVVPD3DHV3RGJW7PANCNFSM4K5CVKUQ> .

[mhdawson]

By my count we have >1/2 TSC as +1s and no objections. Considering approved will start on onboarding checklist. With the addition of the other 2 members we will also no longer be over the corporate limit for IBM.

• Confirm that the new member has read, understands, and agrees to uphold the
  Code of Conduct.
  @gireeshpunathil can you comment in this issue confirming this.
• 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.
• Invite them to the HackerOne Node.js team.
• Add them to the tsc and crypto-export mailing lists.
• Update the @nodejs/node repository README to reflect membership in the TSC.
• Update https://github.com/nodejs/create-node-meeting-artifacts/blob/master/templates/invited_tsc and https://github.com/nodejs/create-node-meeting-artifacts/blob/master/templates/observers_tsc to reflect membership in the TSC.

[mhdawson]

PR to add to meeting issue generator: nodejs/create-node-meeting-artifacts#89

[gireeshpunathil]

I confirm that I (re-)read and understood the said code of conduct. I pledge to uphold its values and maintain its standards

[mhdawson]

Checklist complete, closing.