From 221f298078e90d1c93398a15dba335cab5e186c7 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Thu, 10 Nov 2022 09:03:50 -0800 Subject: [PATCH] meta: be more proactive about removing from teams MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit PR-URL: https://github.com/nodejs/node/pull/45352 Reviewed-By: Antoine du Hamel Reviewed-By: Chengzhong Wu Reviewed-By: Gireesh Punathil Reviewed-By: Geoffrey Booth Reviewed-By: Darshan Sen Reviewed-By: Michaël Zasso Reviewed-By: Matteo Collina Reviewed-By: Beth Griggs Reviewed-By: Colin Ihrig Reviewed-By: Michael Dawson --- doc/contributing/offboarding.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/contributing/offboarding.md b/doc/contributing/offboarding.md index 87f21103540bef..f30688a33d0d87 100644 --- a/doc/contributing/offboarding.md +++ b/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 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.