Use Teams for the "Who to CC in issues chart"

[Fishrock123]

See https://github.com/nodejs/node/blob/master/doc/onboarding-extras.md#who-to-cc-in-issues (Soon to be a table as per https://github.com/Fishrock123/node/blob/doc/improve-onboarding-extras/doc/onboarding-extras.md#who-to-cc-in-issues)

Refs #6548 (comment)

Here's a copy of the (soon to be current) chart directly:

subsystem	maintainers
lib/buffer	@trevnorris
lib/child_process	@cjihrig, @bnoordhuis
lib/cluster	@cjihrig, @bnoordhuis
lib/{crypto,tls,https}	@nodejs/crypto
lib/domains	@misterdjules
lib/{_}http{*}	@indutny, @bnoordhuis, @mscdex, @nodejs/http
lib/net	@indutny, @bnoordhuis, @nodejs/streams
`lib/{_}stream{s	*}`
lib/repl	@Fishrock123
lib/timers	@Fishrock123, @misterdjules
lib/zlib	@indutny, @bnoordhuis
src/async-wrap.*	@trevnorris
src/node_crypto.*	@nodejs/crypto
test/*	@nodejs/testing
tools/eslint, .eslintrc	@silverwind, @Trott
upgrading v8	@bnoordhuis, @targos, @ofrobots
upgrading npm	@thealphanerd, @Fishrock123

Background:

Would much prefer to make these all team references and begin moving away from specific individuals. Doing so has worked effectively for things like lts, documentation, streams, http, and crypto. For instance, I've created a @nodejs/buffer team as an example.

The downside to mentioning specific individuals is that it creates a disincentive for new collaborators to feel empowered to jump in and help with the reviews and puts too much emphasis and burden on specific individuals.

For some areas, yes.

For other parts of core, I think this is still correct until the knowledge becomes more distilled and distributed as more people learn the codebase, and while that is something we should work towards it doesn't necessarily reflect reality.

[jasnell]

The @nodejs/buffer team currently includes @trevnorris, @bnoordhuis, @addaleax and myself.

[misterdjules]

When making changes to V8, it would be great to notify @nodejs/post-mortem, as the tools they build are highly impacted by changes made to V8.

[santigimeno]

Would it be worth adding an entry for the debugger?

[Fishrock123]

@santigimeno Absolutely!

[bnoordhuis]

upgrading v8 @bnoordhuis, @targos, @ofrobots

I'd cc @nodejs/v8 for that.

[rvagg]

@nodejs/build could be mentioned for anything to do with Makefile, vcbuild.bat, gyp, lots of stuff in tools/ including installers. It's a bit scattered but there's a lot of it.

[mcollina]

fs and path are not listed here.

You can add myself for dgram, but maybe we can form up a wg.

[evanlucas]

util and assert are missing as well

[Fishrock123]

fs and path are not listed here.

util and assert are missing as well

Could you suggest people we can list for those? 🐹

[evanlucas]

I know @Trott has messed with assert a bit. You can add me for util. Ben and Colin have spent some time in util as well

[jasnell]

The fs team should most likely include @bnoordhuis, @piscisaureus and @saghul due to the libuv dependency. You can include me because of the Buffer enablement in the API.

[jbergstroem]

Please add @jbergstroem for updating deps/{http-parser, cares}

[addaleax]

I can be added for zlib. :-)

[saghul]

You can add myself for upgrading deps/libuv.

[Fishrock123]

I've made a PR with the notes so far at #6694

[misterdjules]

@Fishrock123 Thank you!