Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 34.2k
doc: update "who to cc in issues" chart#6694
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
Uh oh!
There was an error while loading. Please reload this page.
Conversation
doc/onboarding-extras.md Outdated
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 4746b8eComparedoc/onboarding-extras.md Outdated
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 92c48a9Comparedoc/onboarding-extras.md Outdated
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 2c7251bComparedoc/onboarding-extras.md Outdated
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.
orangemocha commented May 12, 2016
We could add @nodejs/platform-windows for tools/msvs/* (mostly for the MSI). |
Trott commented May 12, 2016
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. |
ronkorving commented May 17, 2016
Feel free to add me to the |
eljefedelrodeodeljefe commented May 25, 2016
@Fishrock123 ping |
MylesBorins commented Jun 6, 2016
@Fishrock123 want me to take this over? |
2c7251b to 2e99bbdCompareFishrock123 commented Jun 17, 2016
Updated, LGTEveryone? |
2e99bbd to 451c1f8CompareMylesBorins commented Jun 17, 2016
LGTM |
2 similar comments
Trott commented Jun 17, 2016
LGTM |
addaleax commented Jun 22, 2016
LGTM |
Trott commented Jun 22, 2016
@RReverser Looks like this PR already updates the who-to-cc for buffer to the correct group. |
RReverser commented Jun 22, 2016
@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 f5cddadCompareRefs: #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.