Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

doc: add offboarding doc #21103

Closed
wants to merge 1 commit into from
Closed

doc: add offboarding doc #21103

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions doc/offboarding.md
View file
Open in desktop
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.