-
Notifications
You must be signed in to change notification settings - Fork 78
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
Node.js Diagnostics WorkGroup Meeting 2020-04-22 #381
Comments
I'd like to discuss nodejs/node#32891. That can be part of the async_hooks stuff at the end. That's the first step in my async_hooks improvement work. :) |
Seems like we have a packed agenda again. Should we prioritize the deep dives for this week, since we didn't do it last time? |
while few items require just few minutes to discuss, the others could potentially take up the whole time. So many be extending the meeting by half an hour and covering deep dive makes sense? |
Does it make sense to run the meeting every week for 1 hour as same as now to reduce the burden for each meeting? |
Most important for me is to have a recording and notes as the timeframe usually doesn't allow me to participate even I'm interested in several topics. |
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made. |
Time
UTC Wed 22-Apr-2020 16:30 (04:30 PM):
Or in your local time:
Links
Agenda
Extracted from diag-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/diagnostics
Invited
Observers/Guests
Notes
The agenda comes from issues labelled with
diag-agenda
across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.Joining the meeting
The text was updated successfully, but these errors were encountered: