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
{{ message }}
This repository was archived by the owner on Jun 24, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 24, 2026. It is now read-only.
The next steps on #55 is to understand the underlying apis we will build on top of. Anyone who is interested in this effort, please react below with the time which works best for you.
馃憤 Friday Sept 11th @ 2pm ET (11pm PT)
馃帀 Friday Sept 11th @ 3pm ET (12pm PT)
鉂わ笍 Monday Sept 14th @ 12pm ET (8am PT)
This is super informal, and to not put too much pressure on @jasnell I hope only folks deeply invested in helping with this effort will join. If James is alright maybe we can record the session for layer viewing.
Ok, looks like Friday Sept 11th @ 2pm ET (12pm PT) is leading. If that is a hard no for anyone, please speak up before then. I will update this issue with the zoom link later today.
I do not have access to add things to the node calendar, I am hoping maybe @jasnell can do that?
@wesleytodd Should we create a summary of our gist conversation somewhere on this repo?
I think it is great context to add, but maybe it would be more helpful to do after our sync so we can make sure it is all on the right track as far as everyone else is concerned?
Hey, so on the theme of getting times wrong....I got the Pacific time on this wrong as well. I really do rely on automation for these issues, because translating them manually is just error prone. So the original goal time was noon in Pacific time. This time is one hour off that (11am). I know I am fine with that, but I figured we should check with our presenter before we solidify it. @jasnell is this time still good for you, or do we need to push it an hour?
Activity
wesleytodd commentedon Sep 9, 2020
Ok, looks like Friday Sept 11th @ 2pm ET (12pm PT) is leading. If that is a hard no for anyone, please speak up before then. I will update this issue with the zoom link later today.
wesleytodd commentedon Sep 9, 2020
Sorry, I should have posted gmt! That is 6:00 PM GMT.
delvedor commentedon Sep 10, 2020
Timezones are hard! The day when all the world will move to UTC will be a great day :P
Just to be clear, this is the time, right?
https://www.timeanddate.com/worldclock/?iso=2020-09-11T18:00:00
ronag commentedon Sep 10, 2020
Please make sure it's in the Node.js Foundation calendar.
ronag commentedon Sep 10, 2020
@wesleytodd Should we create a summary of our gist conversation somewhere on this repo?
wesleytodd commentedon Sep 10, 2020
Yes that is the correct time @delvedor
I do not have access to add things to the node calendar, I am hoping maybe @jasnell can do that?
I think it is great context to add, but maybe it would be more helpful to do after our sync so we can make sure it is all on the right track as far as everyone else is concerned?
wesleytodd commentedon Sep 10, 2020
Hey, so on the theme of getting times wrong....I got the Pacific time on this wrong as well. I really do rely on automation for these issues, because translating them manually is just error prone. So the original goal time was noon in Pacific time. This time is one hour off that (11am). I know I am fine with that, but I figured we should check with our presenter before we solidify it. @jasnell is this time still good for you, or do we need to push it an hour?
ghermeto commentedon Sep 10, 2020
can you record the meeting? I have an appointment tomorrow at noon.
wesleytodd commentedon Sep 11, 2020
EDIT: ongoing conversations, sorry for the churn.
sheplu commentedon Sep 11, 2020
do we have a zoom link for this presentation? or something else ?
wesleytodd commentedon Sep 11, 2020
Yep, just made it: https://zoom.us/j/97827452432
wesleytodd commentedon Sep 12, 2020
Here is the recording: https://www.youtube.com/watch?v=FLZRDbQnNoc