Skip to content

Commit

Permalink
doc: add offboarding doc
Browse files Browse the repository at this point in the history
Add minimal document for what to do when a Collaborator moves to
Collaborator Emeritus or leaves the project.

PR-URL: #21103
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Lance Ball <lball@redhat.com>
Reviewed-By: Matheus Marchini <matheus@sthima.com>
  • Loading branch information
Trott committed Jun 5, 2018
1 parent 327ce2d commit fc3fd60
Showing 1 changed file with 16 additions and 0 deletions.
16 changes: 16 additions & 0 deletions doc/offboarding.md
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.

0 comments on commit fc3fd60

Please sign in to comment.