Skip to content

Commit e2a7928

Browse files
TrottMylesBorins
authored andcommitted
doc: add offboarding doc
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 <[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]>
1 parent 1c211ec commit e2a7928

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

doc/offboarding.md

+16
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
# Offboarding
2+
3+
This document is a checklist of things to do when a Collaborator becomes
4+
Emeritus or leaves the project.
5+
6+
* Remove the Collaborator from the @nodejs/collaborators team.
7+
* Open a fast-track pull request to move the Collaborator to Collaborator
8+
Emeriti in README.md.
9+
* Email the TSC mailing list to notify TSC members that the Collaborator is
10+
moving to Collaborator Emeritus.
11+
* Determine what GitHub teams the Collaborator belongs to. In consultation with
12+
the Collaborator, determine which of those teams they should be removed from.
13+
* Some teams may also require a pull request to remove the Collaborator from
14+
a team listing. For example, if someone is removed from @nodejs/build,
15+
they should also be removed from the Build WG README.md file in the
16+
https://github.com/nodejs/build repository.

0 commit comments

Comments
 (0)