Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

doc: add links in offboarding.md #51440

Merged
merged 2 commits into from
Jan 14, 2024
Merged

doc: add links in offboarding.md #51440

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fad4f82
doc: add links in `offboarding.md`
aduh95 Jan 12, 2024
d23605c
EOL EOF
aduh95 Jan 12, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 9 additions & 4 deletions doc/contributing/offboarding.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
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.
* 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
Expand All @@ -15,6 +15,11 @@ emeritus or leaves the project.
* When in doubt, especially if you are unable to get in contact with the
collaborator, remove them from all teams. It is easy enough to add them
back later, so we err on the side of privacy and security.
* Open an issue in the [build](https://github.com/nodejs/build) repository
titled `Remove Collaborator from Coverity` asking that the collaborator
be removed from the Node.js coverity project if they had access.
* Remove them from the [`@nodejs`](https://github.com/orgs/nodejs/people) GitHub
org unless they are members for a reason other than being a Collaborator.
* [Open an issue](https://github.com/nodejs/build/issues/new) in the
nodejs/build repository titled `Remove Collaborator from Coverity` asking that
the collaborator be removed from the Node.js coverity project if they had
access.

[`@nodejs/collaborators`]: https://github.com/orgs/nodejs/teams/collaborators/members