Skip to content

Commit 221f298

Browse files
Trottdanielleadams
authored andcommittedJan 3, 2023
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>
1 parent 2752f54 commit 221f298

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed
 

‎doc/contributing/offboarding.md

+3
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,9 @@ emeritus or leaves the project.
1212
a team listing. For example, if someone is removed from @nodejs/build,
1313
they should also be removed from the Build WG README.md file in the
1414
<https://github.com/nodejs/build> repository.
15+
* When in doubt, especially if you are unable to get in contact with the
16+
collaborator, remove them from all teams. It is easy enough to add them
17+
back later, so we err on the side of privacy and security.
1518
* Open an issue in the [build](https://github.com/nodejs/build) repository
1619
titled `Remove Collaborator from Coverity` asking that the collaborator
1720
be removed from the Node.js coverity project if they had access.

0 commit comments

Comments
 (0)