You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just a reminder to all @nodejs/collaborators and @nodejs/members .. the next collaborator summit is just two days from now in Berlin. If you're planning to attend, please make sure you register here.
A Project Board has been set up to figure out the schedule.
The Collab Summit is open to all but it is intended to be a face-to-face working session as much as possible. The goal is to get as deep into the technical weeds as necessary to work through any issues we may be working on.
Some schedule highlights already in the agenda:
May 4th
10:00-12:00 HTTP/2 Working Session
13:00-16:00 Streams Working Group
13:00-17:00 Community Committee Open Session
May 5th:
9:00-10:00 N-API Working Session
10:00 - 11:00 Community Committee Closed Session
13:00 - 17:00 Community Committe Open Session
13:00 - 14:00 Promises Discussion
There's plenty of room for more. All working groups and teams are invited to participate and schedule space to meet and discuss.
(Note: please keep this issue open until May 4th. )
The text was updated successfully, but these errors were encountered:
Just a reminder to all @nodejs/collaborators and @nodejs/members .. the next collaborator summit is just two days from now in Berlin. If you're planning to attend, please make sure you register here.
A Project Board has been set up to figure out the schedule.
Full details here
The Collab Summit is open to all but it is intended to be a face-to-face working session as much as possible. The goal is to get as deep into the technical weeds as necessary to work through any issues we may be working on.
Some schedule highlights already in the agenda:
There's plenty of room for more. All working groups and teams are invited to participate and schedule space to meet and discuss.
(Note: please keep this issue open until May 4th. )
The text was updated successfully, but these errors were encountered: