mirrors/nodejs
mirrors/nodejs
0
0
Fork 0
mirror of https://github.com/nodejs/node.git synced 2024-11-30 23:43:09 +01:00
Code Issues Releases Activity
01bc8e6fd8
nodejs/doc/contributing/offboarding.md
Michael Dawson a199387f04 doc: make contributing info more discoverable 
There are been several discussions in recent PRs about
the docs related to contributing not being very discoverable.
Move these docs from doc/guides/ to doc/contributing.

Signed-off-by: Michael Dawson <mdawson@devrus.com>

PR-URL: https://github.com/nodejs/node/pull/41408
Reviewed-By: Franziska Hinkelmann <franziska.hinkelmann@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Derek Lewis <DerekNonGeneric@inf.is>
Reviewed-By: Mary Marchini <oss@mmarchini.me>
Reviewed-By: James M Snell <jasnell@gmail.com>
2022-01-18 14:24:30 -05:00

943 B
Raw Blame History

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 the collaborator emeriti list in README.md.
  • 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.
  • Open an issue in the build repository titled Remove Collaborator from Coverity asking that the collaborator be removed from the Node.js coverity project if they had access.