Skip to content

Latest commit

 

History

History
58 lines (51 loc) · 3.92 KB

ONBOARDING.md

File metadata and controls

58 lines (51 loc) · 3.92 KB

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

Onboarding/offboarding of regular members