-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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: document the performance team #12213
Conversation
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.
Wow this is quick. Thanks!
@gibfahn thanks but I don't consider myself a performance expert :) gonna remove myself from the team. |
I think @mcollina and @trevnorris are good candidates for the team instead. |
I've just request access. |
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.
LGTM
Also @petkaantonov if he is still active. |
One last: @benjamingr, sorry about the spam. P.S. I'm probably missing other good candidates :) |
@@ -27,6 +27,7 @@ | |||
| `test/*` | @nodejs/testing | | |||
| `tools/eslint`, `.eslintrc` | @not-an-aardvark, @silverwind, @trott | | |||
| async_hooks | @nodejs/diagnostics | | |||
| performance | @nodejs/performance | |
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.
Just noticed.. should we replace the row for benchmark/*
above too?
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 considered it, but I'm not sure. That's probably a question for @nodejs/benchmarking.
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.
It already has @nodejs/benhmarking and mscdex is not part of that team but is interested in the core benchmarks
Maybe @fhinkel would be interested. |
Sure |
Added all the people mentioned, that way they can leave if they want. EDIT: You're all team maintainers, so if you want to add someone go for it!
@lpinca The idea isn't that these are a list of performance experts (otherwise it'd probably be a short list 😁 ). It's just to have a list of people who are willing to look at performance issues and PRs. Feel free to remove yourself if you want, but being in the team doesn't mean you have to approve PRs or anything. |
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.
LGTM
@@ -27,6 +27,7 @@ | |||
| `test/*` | @nodejs/testing | | |||
| `tools/eslint`, `.eslintrc` | @not-an-aardvark, @silverwind, @trott | | |||
| async_hooks | @nodejs/diagnostics | | |||
| performance | @nodejs/performance | |
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.
It already has @nodejs/benhmarking and mscdex is not part of that team but is interested in the core benchmarks
Can be cc'ed with `@nodejs/performance`. PR-URL: nodejs#12213 Refs: nodejs#12194 (comment) Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Can be cc'ed with `@nodejs/performance`. PR-URL: nodejs#12213 Refs: nodejs#12194 (comment) Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Can be cc'ed with `@nodejs/performance`. PR-URL: #12213 Refs: #12194 (comment) Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Can be cc'ed with `@nodejs/performance`. PR-URL: #12213 Refs: #12194 (comment) Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Can be cc'ed with `@nodejs/performance`. PR-URL: nodejs/node#12213 Refs: nodejs/node#12194 (comment) Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Can be cc'ed with
@nodejs/performance
.I added some people: @mscdex @vsemozhetbyt @joyeecheung @TimothyGu @lpinca
If anyone else wants to join and be cc/ed on issues, feel free to request access (or remove yourself if you don't want to be on the team).
Link to team
Refs: #12194 (comment)
Checklist
Affected core subsystem(s)