From ec1a4a9e3a752a2fc26d6a3e0a77a7e16ba7817e Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Sat, 2 Jun 2018 23:24:23 +0200 Subject: [PATCH] doc: add offboarding doc Add minimal document for what to do when a Collaborator moves to Collaborator Emeritus or leaves the project. --- doc/offboarding.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/offboarding.md diff --git a/doc/offboarding.md b/doc/offboarding.md new file mode 100644 index 00000000000000..5b7a1e1231e8d7 --- /dev/null +++ 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.