-
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 Foundation Diagnostics WorkGroup Meeting 2020-01-15 #346
Comments
We should probably remove #124, there was no updates on the last few meetings, and AFAIK there's nothing to be discussed (we're just waiting for someone to invest time on this) |
That's me now. I claimed responsibility for async_hooks at Node+JS Interactive and have been working on some things there albeit a little slowly as I've been busy with job interviews. I'd like to keep it on the agenda so I can discuss where it's at and where I'm hoping to go with it. :) |
Makes sense, let's keep it then :) |
I also interested in async_hooks area. But as mentioned at a few places/doodles the timeslot for the diagnostics meeting doesn't work for me. But I usually read meeting notes and/or watch the recordings. @Qard Please let me know if you need some assistance in this area. Even if I might not be able to spent that much time on this continously I'm available at least for smaller tasks. Watching issues/PRs anyway. |
@Flarna - we attempted to arrive at a timeslot that works for everyone, but failed. I am going to setup another doodle this week, stay tuned! |
meeting happened, closing |
Time
UTC Wed 15-Jan-2020 18:30 (06: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: