-
Notifications
You must be signed in to change notification settings - Fork 30.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add minimal document for what to do when a Collaborator moves to Collaborator Emeritus or leaves the project.
- Loading branch information
Showing
1 changed file
with
16 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
# 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. |