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 Nov 9, 2017. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 9, 2017. It is now read-only.
Node.js Foundation Core Technical Committee (CTC) Meeting 2017-03-22 #82
The agenda comes from issues labelled with ctc-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
Uberconference; participants should have the link & numbers, contact me if you don't.
Public participation
We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.
Many of us will be on IRC in #node-dev on Freenode if you'd like to interact, we have a Q/A session scheduled at the end of the meeting if you'd like us to discuss anything in particular. @nodejs/collaborators in particular if there's anything you need from the CTC that's not worth putting on as a separate agenda item, this is a good place for it.
Only one item on the agenda (so far) but it's a big one.
In addition to the agenda item, here are ctc-review items (which will not be discussed in the meeting but for which @nodejs/ctc attention has been requested):
I won't be able to make it. The move from midnight to 1am makes it a lot more difficult.
@cjihrig Can you update the availability spreadsheet to reflect this and I'll re-run the meeting-fairness algorithm? (If it's all up to date and it's just a matter of shifting it all by one hour to reflect current reality, I can do that for you if you prefer.)
I've updated the spreadsheet. Based on the Amsterdam and Moscow times, it doesn't look like shifting the meeting back an hour is an option. If I'm the only one really impacted by this, I wouldn't worry about it... there's always GitHub.
Activity
cjihrig commentedon Mar 20, 2017
I won't be able to make it. The move from midnight to 1am makes it a lot more difficult.
Trott commentedon Mar 20, 2017
Only one item on the agenda (so far) but it's a big one.
In addition to the agenda item, here are ctc-review items (which will not be discussed in the meeting but for which @nodejs/ctc attention has been requested):
Trott commentedon Mar 20, 2017
@cjihrig Can you update the availability spreadsheet to reflect this and I'll re-run the meeting-fairness algorithm? (If it's all up to date and it's just a matter of shifting it all by one hour to reflect current reality, I can do that for you if you prefer.)
cjihrig commentedon Mar 20, 2017
I've updated the spreadsheet. Based on the Amsterdam and Moscow times, it doesn't look like shifting the meeting back an hour is an option. If I'm the only one really impacted by this, I wouldn't worry about it... there's always GitHub.
Fishrock123 commentedon Mar 20, 2017
Oh, yeah. 1am. Also won't make it. Someone else will have to stream. I'll try to remember to update the sheet.
fhinkel commentedon Mar 20, 2017
I also won't be able to make it this week.
addaleax commentedon Mar 20, 2017
ditto, I won’t be able to be there.
misterdjules commentedon Mar 20, 2017
I won't be able to attend.
mhdawson commentedon Mar 21, 2017
added ctc-review to nodejs/node#11975 as well.
I might make it but more likely not, presenting "Node.js ask us anything" with Sam at Devoxx from 8:30- 9:30 PST.
joshgav commentedon Mar 21, 2017
cc @jasongin re #11975
evanlucas commentedon Mar 21, 2017
I probably won't make it tonight either
joshgav commentedon Mar 24, 2017
Notes in #84