2018-06-02 23:24:23 +02:00
|
|
|
# Offboarding
|
|
|
|
|
2021-07-14 00:15:59 +02:00
|
|
|
This document is a checklist of things to do when a collaborator becomes
|
|
|
|
emeritus or leaves the project.
|
2018-06-02 23:24:23 +02:00
|
|
|
|
2024-01-14 11:26:35 +01:00
|
|
|
* Remove the collaborator from the [`@nodejs/collaborators`][] team.
|
2021-07-14 00:15:59 +02:00
|
|
|
* 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
|
2019-09-01 08:18:32 +02:00
|
|
|
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
|
2020-04-06 05:26:24 +02:00
|
|
|
<https://github.com/nodejs/build> repository.
|
2022-11-10 18:03:50 +01:00
|
|
|
* 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
|
|
|
|
back later, so we err on the side of privacy and security.
|
2024-01-14 11:26:35 +01:00
|
|
|
* Remove them from the [`@nodejs`](https://github.com/orgs/nodejs/people) GitHub
|
|
|
|
org unless they are members for a reason other than being a Collaborator.
|
|
|
|
* [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
|