Onboarding/Offboarding

Please refer to the Establishment of the TSC in the TSC Charter. In the event that there is a contradiction between that document and this document, the contradictory elements in this document are invalid and are superseded by the TSC Charter.

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 mailing list: https://github.com/nodejs/email/edit/main/iojs.org/aliases.json
• 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.
• Invite them to the project's 1Password account, once they accept confirm them and add them to the owners group.
• Update https://github.com/nodejs/create-node-meeting-artifacts/blob/main/templates/invited_tsc to reflect membership in the TSC.
• 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.

Offboarding of voting members

• Remove them from the following GitHub orgs unless they are members for a reason other than TSC membership:
  • @nodejs-private
  • @nodejs
  • @pkgjs (unless they're listed on the MEMBERS list)
• Change the member's role from Owner to Member (unless they have Owner role for a reason other than TSC membership) in the following GitHub orgs:
  • @nodejs-private
  • @nodejs
  • @pkgjs (unless they're listed on ADMINISTRATIVE-MEMBERS)
• Remove the member from the following teams:
  • @nodejs/tsc
  • @nodejs/security-tsc
  • @nodejs-private/security-tsc
  • @pkgjs/node-tsc
• Remove them from the HackerOne Node.js team unless they need access for a reason other than TSC membership.
• Remove them from the tsc mailing lists: https://github.com/nodejs/email/edit/main/iojs.org/aliases.json.
• Remove them from the nodejs-tsc Google Group.
• Remove them from the owners group in the project's 1Password account.
• Update the @nodejs/node repository README to reflect membership in the TSC. In all likelihood, they should be listed as TSC regular members.
• Update https://github.com/nodejs/create-node-meeting-artifacts/blob/main/templates/invited_tsc to reflect membership in the TSC.
• Remove them from the #nodejs-tsc channel on the OpenJS Slack. If they are a member of the #nodejs-personnel channel, remove them from that channel as well.

Onboarding/offboarding of regular members

• Update https://github.com/nodejs/create-node-meeting-artifacts/blob/main/templates/invited_tsc to reflect membership in the TSC.