-
Notifications
You must be signed in to change notification settings - Fork 7
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
Looking for a chair for upcoming performance meetings #143
Comments
I usually have a regularly scheduled meeting on my work at the same time as the performance team meeting, so even if I want to be the |
I served as a |
Seems to be a universal experience that the time slot is not great. Same sentiment here. 🙈 |
The same applies to me. I'm wondering if we could integrate the nodejs/diagnostics with nodejs/performance meetings. Both meetings don't fit into my calendar, but we could find a better time and host both topics. |
@RafaelGSS I liked the idea, currently I don't think the topics for the performance will take the whole hour, if we join both topics we maybe can use the whole time of the meeting and cover all the topics with more people. |
Makes sense to me, especially given most diag wg sessions have mainly been about async_hooks perf for awhile now. 😅 |
Would somebody like to configure meeting notes script and open a calendar poll to figure out the best time to change the meetings? |
Hi everybody,
Due to personal reasons & developments, I'm having hard time chairing the performance meetings. Currently, I'm the only person who has access to Youtube and Zoom, that regularly attends the meetings.
Therefore, I'd like to publicly ask if there is a Node.js collaborator who'd like to chair the upcoming performance meetings?
Ideally, this person will get access to Zoom & Youtube accounts of Node.js (through GitHub.com/nodejs/admin) and start & live-stream meetings, and take meeting notes.
PS: We could also potentially explore to have a
co-chair
in case the new chair is unavailable in the future.cc @nodejs/performance @nodejs/tsc
The text was updated successfully, but these errors were encountered: