0
0
mirror of https://github.com/nodejs/node.git synced 2024-12-01 16:10:02 +01:00
nodejs/doc/guides/offboarding.md
ConorDavenport bf7409e974
doc: improve doc/markdown file organization coherence
* Updated cpp style guide file name and location and fixed links to
  this file.

* Updated collaborator guide file name and location and fixed links
  to this file.

* Updated documentation style guide file name and location and updated
  links referencing the file.

* Moved files to appropriate location and updated naming style for
  some of them.

Fixes: https://github.com/nodejs/node/issues/31741

PR-URL: https://github.com/nodejs/node/pull/31792
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
2020-03-04 13:13:07 +00:00

17 lines
827 B
Markdown

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