-
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 2023-05-02 #612
Comments
@mhdawson: are these group meetings closed group meetings or can someone which is not part of the diagnostics team also take part? |
@dygabo the meetings are open, so feel free to join using the zoom link in the issue. |
I have a conflict for the first half the meeting but hope to make the second half. |
I won't be able to join again... I have some conflicts. As an update, I'm not planning to pursue work #502 due to:
If someone wants to take the lead on that, feel free. Otherwise, I'm fine closing it as |
Looks like non of the people who chair/lead the meeting could make it this time as when I joined late the meeting was not running. @dygabo this happens on occasion, hope to see you at the next meeting. |
sure, thanks @mhdawson. I'll try to keep an eye on the repo and stay up to date, maybe also join with next occasion. |
@dygabo follow our agenda at: https://nodejs.org/calendar |
I was on vacation but missed to update here on my status - apologies. |
Time
UTC Tue 02-May-2023 15:30 (03: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: