-
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 2018-05-02 #187
Comments
Unfortunately I'm at a one day conference on Wednesday this week so I will not be able to make it. One small update is that I've talked to @richardlau who is working on bringing node-report into core as discussed in the summit. I'm hoping he will have a list of steps/rough idea of timeline in the next week or so. |
We may want to add discussing nodejs/node#20274 to the agenda. |
I'd like to add #186 to the agenda. Shouldn't take more than 5-10 minutes :) |
(and to also join the meeting of course) |
I would also like to add #188 to the agenda. |
#186, #188 and nodejs/node#20274 all on agenda now. |
Time
UTC Wed 02-May-2018 18:00 (06:00 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
nodejs/TSC
Invited
Observers
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: