Description
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.