1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: add links in offboarding.md

Browse Source 
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>
This commit is contained in:
Antoine du Hamel 2024-01-14 11:26:35 +01:00 committed by GitHub
parent ee5cfcb5f7
commit 9fce1df548
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/contributing/offboarding.md
View File

@ -3,7 +3,7 @@
This document is a checklist of things to do when a collaborator becomes This document is a checklist of things to do when a collaborator becomes
emeritus or leaves the project. emeritus or leaves the project.
* Remove the collaborator from the @nodejs/collaborators team. * Remove the collaborator from the [`@nodejs/collaborators`][] team.
* Open a fast-track pull request to move the collaborator to the collaborator * Open a fast-track pull request to move the collaborator to the collaborator
emeriti list in README.md. emeriti list in README.md.
* Determine what GitHub teams the collaborator belongs to. In consultation with * Determine what GitHub teams the collaborator belongs to. In consultation with
@ -15,6 +15,11 @@ emeritus or leaves the project.
* When in doubt, especially if you are unable to get in contact with the * 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 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. back later, so we err on the side of privacy and security.
* Open an issue in the [build](https://github.com/nodejs/build) repository * Remove them from the [`@nodejs`](https://github.com/orgs/nodejs/people) GitHub
titled `Remove Collaborator from Coverity` asking that the collaborator org unless they are members for a reason other than being a Collaborator.
be removed from the Node.js coverity project if they had access. * [Open an issue](https://github.com/nodejs/build/issues/new) 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.
[`@nodejs/collaborators`]: https://github.com/orgs/nodejs/teams/collaborators/members