| Server IP : 34.87.99.72 / Your IP : 216.73.216.122 Web Server : Apache/2.4.46 (Unix) OpenSSL/1.1.1n System : Linux zlock-bitnami-lamp-prod-v2-vm 4.19.0-16-cloud-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 User : bitnami ( 1000) PHP Version : 7.4.18 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : OFF Directory : /proc/thread-self/root/usr/share/doc/nodejs/guides/ |
Upload File : |
# Offboarding
This document is a checklist of things to do when a Collaborator becomes
Emeritus or leaves the project.
* Remove the Collaborator from the @nodejs/collaborators team.
* Open a fast-track pull request to move the Collaborator to Collaborator
Emeriti in README.md.
* Email the TSC mailing list to notify TSC members that the Collaborator is
moving to Collaborator Emeritus.
* Determine what GitHub teams the Collaborator belongs to. In consultation with
the Collaborator, determine which of those teams they should be removed from.
* Some teams may also require a pull request to remove the Collaborator from
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.