Add minimal document for what to do when a Collaborator moves to
Collaborator Emeritus or leaves the project.

PR-URL: https://github.com/nodejs/node/pull/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>
This commit is contained in:
Rich Trott 2018-06-02 23:24:23 +02:00 коммит произвёл Myles Borins
Родитель 1c211ec901
Коммит e2a792866c
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 933B01F40B5CA946
1 изменённых файлов: 16 добавлений и 0 удалений

16
doc/offboarding.md Normal file
Просмотреть файл

@ -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.