GeezerVison

The World Wide Web, restored to 800 pixels of glory.

GeezerVison is showing github.com — meta: be more proactive about removing from teams · nodejs/node@221f298

File tree

Expand file treeCollapse file tree

Open diff view settings

Filter options

doc/contributing
- offboarding.md

Expand file treeCollapse file tree

Open diff view settings

Collapse file

`‎doc/contributing/offboarding.md‎`

Copy file name to clipboardExpand all lines: doc/contributing/offboarding.md

+3Lines changed: 3 additions & 0 deletions

Display the source diff
Display the rich diff

Original file line number	Diff line number	Diff line change
`@@ -12,6 +12,9 @@ emeritus or leaves the project.`
`12`	`12`	`a team listing. For example, if someone is removed from @nodejs/build,`
`13`	`13`	`they should also be removed from the Build WG README.md file in the`
`14`	`14`	`<https://github.com/nodejs/build> repository.`
	`15`	`+ * When in doubt, especially if you are unable to get in contact with the`
	`16`	`+ collaborator, remove them from all teams. It is easy enough to add them`
	`17`	`+ back later, so we err on the side of privacy and security.`
`15`	`18`	`* Open an issue in the [build](https://github.com/nodejs/build) repository`
`16`	`19`	titled `Remove Collaborator from Coverity` asking that the collaborator
`17`	`20`	`be removed from the Node.js coverity project if they had access.`

0 commit comments

Comments

0 (0)

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.