Skip to content

ONBOARDING.md

Latest commit

 

History

History
44 lines (39 loc) · 2.82 KB

ONBOARDING.md

File metadata and controls

44 lines (39 loc) · 2.82 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

  • 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.

Offboarding

  • Remove the member from the @nodejs/tsc and @nodejs/security-tsc teams.
  • Remove them from the HackerOne Node.js team.
  • Change the member's role in the GitHub nodejs organization to Member unless they have Owner role for a reason other than TSC membership.
  • Remove them from the @nodejs-private/security-tsc team.
  • Remove them from the @nodejs-private org unless they are members for a reason other than TSC membership.
  • Remove them from the @pkgjs/node-tsc team
  • Remove them from the @pkgjs org unless they are members for a reason other than TSC membership.
  • Remove them from the tsc and crypto-export mailing lists.
  • Remove them from the nodejs-tsc Google Group.
  • Update the @nodejs/node repository README to reflect membership in the TSC. In all likelihood, they should be listed as TSC Emeritus.
  • 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.