Server : nginx/1.20.1 System : Linux ccpf-production-2021 5.4.0-148-generic #165-Ubuntu SMP Tue Apr 18 08:53:12 UTC 2023 x86_64 User : forge ( 1000) PHP Version : 7.4.21 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare, Directory :  /usr/share/doc/nodejs/guides/

Upload File : current_dir [ Writeable ] document_root [ Writeable ]

# 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.