-
Notifications
You must be signed in to change notification settings - Fork 6
Follow up on July 3rd #5
Comments
I think we should schedule another meeting :) |
@benjamingr What would be the agenda? Discussing the state of nodejs/node#20097 seems like it would be helpful. Any other topic in mind? |
In either case I'd rather schedule after NodeSummit which is probably keeping everyone busy. |
Any further details on that? Do you have a link to that discussion?
What spec update? Do you have a link to share?
What do you mean by "unhandled rejection stuff"? Let's have an agenda that is as detailed as possible so that people can adequately prepare ahead of the meeting. |
Sure, it's at
Not yet, not sure where that stands, @littledan might know more.
Well, we discussed a bunch of possibly useful hooks with the V8 people at the summit, this is just for a general update about it mostly. Sorry it's not more detailed. |
Can you elaborate on what you'd want to discuss from that?
If this item is just an update and there's no clear value in discussing in person, can that update be shared online on GH, as a Google doc, or in any other way that doesn't take valuable time from people's schedule? |
We might also want to come up with some goals that align with the Vancouver collaborators summit's dates so that those of us who will be there can use the opportunity of meeting face to face to make progress on specific topics. |
This issue is a reminder and the action item we agreed on to track our progress in 3 weeks and see if an additional meeting is required.
The text was updated successfully, but these errors were encountered: