Nodejs/node
1
0
Fork 0
mirror of https://github.com/nodejs/node.git synced 2024-11-21 10:59:27 +00:00
Code Issues Actions 25 Packages Projects Releases Wiki Activity
main
node/doc/contributing/offboarding.md
Antoine du Hamel 9fce1df548
doc: add links in offboarding.md 
PR-URL: https://github.com/nodejs/node/pull/51440
Reviewed-By: Vinícius Lourenço Claro Cardoso <contact@viniciusl.com.br>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>
2024-01-14 10:26:35 +00:00

1.4 KiB
Raw Permalink Blame History

Offboarding

This document is a checklist of things to do when a collaborator becomes emeritus or leaves the project.

  • Remove the collaborator from the @nodejs/collaborators team.
  • Open a fast-track pull request to move the collaborator to the collaborator emeriti list in README.md.
  • Determine what GitHub teams the collaborator belongs to. In consultation with the collaborator, determine which of those teams they should be removed from.
    • Some teams may also require a pull request to remove the collaborator from a team listing. For example, if someone is removed from @nodejs/build, they should also be removed from the Build WG README.md file in the https://github.com/nodejs/build repository.
    • When in doubt, especially if you are unable to get in contact with the collaborator, remove them from all teams. It is easy enough to add them back later, so we err on the side of privacy and security.
  • Remove them from the @nodejs GitHub org unless they are members for a reason other than being a Collaborator.
  • Open an issue in the nodejs/build repository titled Remove Collaborator from Coverity asking that the collaborator be removed from the Node.js coverity project if they had access.