meta: be more proactive about removing from teams

PR-URL: #45352
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com>
Reviewed-By: Darshan Sen <raisinten@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Beth Griggs <bethanyngriggs@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>

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.