| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
1 parent 58d2442 commit 0dffb9f
1 file changed
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -3,7 +3,7 @@ | |||
| 3 | 3 | This document is a checklist of things to do when a collaborator becomes | |
| 4 | 4 | emeritus or leaves the project. | |
| 5 | 5 | ||
| 6 | - * Remove the collaborator from the @nodejs/collaborators team. | ||
| 6 | + * Remove the collaborator from the [`@nodejs/collaborators`][] team. | ||
| 7 | 7 | * Open a fast-track pull request to move the collaborator to the collaborator | |
| 8 | 8 | emeriti list in README.md. | |
| 9 | 9 | * Determine what GitHub teams the collaborator belongs to. In consultation with | |
@@ -15,6 +15,11 @@ emeritus or leaves the project. | |||
| 15 | 15 | * When in doubt, especially if you are unable to get in contact with the | |
| 16 | 16 | collaborator, remove them from all teams. It is easy enough to add them | |
| 17 | 17 | back later, so we err on the side of privacy and security. | |
| 18 | - * Open an issue in the [build](https://github.com/nodejs/build) repository | ||
| 19 | - titled `Remove Collaborator from Coverity` asking that the collaborator | ||
| 20 | - be removed from the Node.js coverity project if they had access. | ||
| 18 | + * Remove them from the [`@nodejs`](https://github.com/orgs/nodejs/people) GitHub | ||
| 19 | + org unless they are members for a reason other than being a Collaborator. | ||
| 20 | + * [Open an issue](https://github.com/nodejs/build/issues/new) in the | ||
| 21 | + nodejs/build repository titled `Remove Collaborator from Coverity` asking that | ||
| 22 | + the collaborator be removed from the Node.js coverity project if they had | ||
| 23 | + access. | ||
| 24 | + | ||
| 25 | + [`@nodejs/collaborators`]: https://github.com/orgs/nodejs/teams/collaborators/members | ||
| Back | FazBrowse Home | New Git URL |
0 commit comments