doc: add offboarding doc

Add minimal document for what to do when a Collaborator moves to Collaborator Emeritus or leaves the project. PR-URL: nodejs#21103 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Vse Mozhet Byt <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Lance Ball <[email protected]> Reviewed-By: Matheus Marchini <[email protected]>
Trott · Jun 5, 2018 · fc3fd60 · fc3fd60
1 parent 327ce2d
commit fc3fd60
Showing 1 changed file with 16 additions and 0 deletions.
diff --git a/doc/offboarding.md b/doc/offboarding.md
@@ -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.