daohualiuxiang
/
node
mirror of https://github.com/nodejs/node.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
node/doc/contributing/offboarding.md

21 lines
1.1 KiB
Markdown
Raw Normal View History

doc: add offboarding doc 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>
2018-06-03 05:24:23 +08:00
# Offboarding
doc: standardize on not capitalizing _collaborator_ Sometimes we capitalize _collaborator_ and sometimes not. After consulting the Microsoft Style Guide and The Chicago Manual of Style, I've concluded it is best to not capitalize it. For consistency, apply that to our various .md files. Refs: https://docs.microsoft.com/en-us/style-guide/capitalization PR-URL: https://github.com/nodejs/node/pull/39379 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Zijian Liu <lxxyxzj@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: James M Snell <jasnell@gmail.com>
2021-07-14 06:15:59 +08:00
This document is a checklist of things to do when a collaborator becomes
emeritus or leaves the project.
doc: add offboarding doc 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>
2018-06-03 05:24:23 +08:00
doc: standardize on not capitalizing _collaborator_ Sometimes we capitalize _collaborator_ and sometimes not. After consulting the Microsoft Style Guide and The Chicago Manual of Style, I've concluded it is best to not capitalize it. For consistency, apply that to our various .md files. Refs: https://docs.microsoft.com/en-us/style-guide/capitalization PR-URL: https://github.com/nodejs/node/pull/39379 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Zijian Liu <lxxyxzj@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: James M Snell <jasnell@gmail.com>
2021-07-14 06:15:59 +08:00
* 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
doc: use consistent indenting for unordered list items Address Markdownlint MD007 rule. Default suggestion is 2 space indenting for unordered list items. PR-URL: https://github.com/nodejs/node/pull/29390 Reviewed-By: David Carlier <devnexen@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
2019-09-01 14:18:32 +08:00
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
doc: add angle brackets around implicit links PR-URL: https://github.com/nodejs/node/pull/32676 Reviewed-By: Rich Trott <rtrott@gmail.com>
2020-04-06 11:26:24 +08:00
<https://github.com/nodejs/build> repository.
meta: be more proactive about removing from teams PR-URL: https://github.com/nodejs/node/pull/45352 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com> Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Beth Griggs <bethanyngriggs@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com>
2022-11-11 01:03:50 +08:00
* 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.
doc: add info on project's usage of coverity Document project's used of coverity and how collaborators can get access. Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: https://github.com/nodejs/node/pull/40506 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Richard Lau <rlau@redhat.com>
2021-10-19 05:18:29 +08:00
* 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.