-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: update "who to cc in issues" chart #6694
Conversation
| `lib/child_process` | @cjihrig, @bnoordhuis | | ||
| `lib/cluster` | @cjihrig, @bnoordhuis | | ||
| `lib/assert` | @Trott | | ||
| `lib/buffer` | @trevnorris, @nodejs/buffer | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@trevnorris ∈ @nodejs/buffer :)
0b99265
to
4746b8e
Compare
| `lib/{_}http{*}` | @indutny, @bnoordhuis, @mscdex, @nodejs/http | | ||
| `lib/net` | @indutny, @bnoordhuis, @nodejs/streams | | ||
| `lib/fs`, `src/{fs|file}` | @bnoordhuis, @jasnell, @saghul, @trevnorris | | ||
| `lib/{_}http{*}` | @bnoordhuis, @indutny, @mscdex, @nodejs/http | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/@mscdex//
I am already in in nodejs/http
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As is @indutny ... I can add @bnoordhuis to it right now also
4746b8e
to
92c48a9
Compare
| `lib/{crypto,tls,https}` | @nodejs/crypto | | ||
| `lib/domains` | @misterdjules | | ||
| `lib/{_}http{*}` | @indutny, @bnoordhuis, @mscdex, @nodejs/http | | ||
| `lib/net` | @indutny, @bnoordhuis, @nodejs/streams | | ||
| `lib/fs`, `src/{fs|file}` | @bnoordhuis, @jasnell, @saghul, @trevnorris | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have created the nodejs/fs team with these initial members
92c48a9
to
2c7251b
Compare
| upgrading npm | @thealphanerd, @fishrock123 | | ||
| upgrading v8 | @nodejs/v8, @nodejs/post-mortem | | ||
| upgrading npm | @fishrock123, @thealphanerd | | ||
| upgrading c-ares | @jbergstroem, @nodejs/http | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wrong line for nodejs/http
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(we store it as deps/cares
)
Hopefully we can use this as part of the bot at some stage?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've been thinking we could re-use the bot's logic for resolving PR labels, for /cc-ing as well. Who to /cc for which label could be read from this file.
We could add @nodejs/platform-windows for tools/msvs/* (mostly for the MSI). |
LGTM once the c-ares/http error on line 25 is fixed and nodejs/http is added to line 26 (http-parser). IMO, other nits/comments can be addressed now or in subsequent PRs. Fine by me either way. |
Feel free to add me to the |
@Fishrock123 ping |
@Fishrock123 want me to take this over? |
2c7251b
to
2e99bbd
Compare
Updated, LGTEveryone? |
2e99bbd
to
451c1f8
Compare
LGTM |
2 similar comments
LGTM |
LGTM |
@RReverser Looks like this PR already updates the who-to-cc for buffer to the correct group. |
@Trott. Great! LGTM. |
Refs: nodejs#6655 PR-URL: nodejs#6694 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ingvar Stepanyan <[email protected]>
451c1f8
to
f5cddad
Compare
Refs: #6655 PR-URL: #6694 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ingvar Stepanyan <[email protected]>
Refs: #6655 PR-URL: #6694 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ingvar Stepanyan <[email protected]>
Refs: #6655 PR-URL: #6694 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ingvar Stepanyan <[email protected]>
Refs: #6655 PR-URL: #6694 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ingvar Stepanyan <[email protected]>
Refs: #6655 PR-URL: #6694 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ingvar Stepanyan <[email protected]>
Refs: #6655 PR-URL: #6694 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ingvar Stepanyan <[email protected]>
Refs: #6655 PR-URL: #6694 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ingvar Stepanyan <[email protected]>
Refs: #6655 PR-URL: #6694 Reviewed-By: Myles Borins <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ingvar Stepanyan <[email protected]>
Checklist
Affected core subsystem(s)
doc
Description of change
See #6655
@nodejs/collaborators please let us know if you think you should be listed here or not.