-
Notifications
You must be signed in to change notification settings - Fork 59
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
Agenda for Diagnostics session at collaborator summit #71
Comments
This is an agenda for one specific session at the summit, right? If so, can you add the name of the session to the title of this issue? Otherwise it looks like it's supposed to be an agenda for the entire summit. |
I guess this would be for the diagnostics session? Could you please adjust the title? |
@jasnell will not be at the Berlin summit. |
I would love to attend this and I am currently doing a lot of research on this and in general I would love to attend this session - does this overlap with the modules team working group? Also note there is specifically a promises workshop at a later point and I was planning to talk about use cases for the promise hooks there :) |
@mcollina yes will be for the diagnostics session. |
I did mention the promises workshop but other people in the meeting thought it would be covering different topics. As long as its covered in one of the 2 I think people will be happy. |
RE "async terminology", please see PR #197 which describes the current direction & set of terms. |
Meeting Link: https://chime.aws/1822360907 |
Just making sure that this is clear - you won't need an account but can call in as a guest with the client. Also with the client you can share your screen with others in the room as well as remote. |
link to node-report WIP PR: nodejs/node#19661 |
@gtewallace @nodejs/user-feedback Question from this group: |
Diagnostics Session Summary
|
First cut please comment:
Present
Yunong
Anna
Joyee
Vladimir
Bethany
Dan
Stephan
Mark
Thomas
Jan
Jeremiah
Ruben
Matteo
Benjamin
Maya
Ali
Anatolli
Greoge
Greg
Michael
The text was updated successfully, but these errors were encountered: