meta: be more proactive about removing from teams

PR-URL: #45352
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: Gireesh Punathil <[email protected]>
Reviewed-By: Geoffrey Booth <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Beth Griggs <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>

Author: Trott

doc/contributing/offboarding.md

@@ -12,6 +12,9 @@ emeritus or leaves the project.
     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.
 * Open an issue in the [build](https://github.com/nodejs/build) repository
   titled `Remove Collaborator from Coverity` asking that the collaborator
   be removed from the Node.js coverity project if they had access.