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-02-15 #70
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.
(Mentioning @fhinkel in a comment for notification purposes as I messed up and didn't include the @-mention originally when opening the issue. Sorry for the spam, everyone else.)
I'll be missing most or all of the meeting, and it's 3AM for Rod, so he's missing it to almost certainly. It's a pretty slim agenda right now. Two of the three issues that are on the agenda were put there by @jasnell. Maybe he can run the meeting? And hopefully someone volunteers to take notes...
Perhaps we should skip it? There seems to be consensus on nodejs/node#10467, nodejs/TSC#174 has no significant new developments, and I don't think we're remotely ready to discuss nodejs/node#11233, never mind reaching a decision.
Speaking for myself, I haven't even seriously started reading through all the discussion threads, let alone form a well-reasoned opinion.
Activity
Trott commentedon Feb 13, 2017
CTC review issues:
Trott commentedon Feb 13, 2017
(Mentioning @fhinkel in a comment for notification purposes as I messed up and didn't include the @-mention originally when opening the issue. Sorry for the spam, everyone else.)
targos commentedon Feb 13, 2017
I'll be in a train at the time of the meeting. I will try to connect over 4G but apologize in advance in case I can't make it.
mhdawson commentedon Feb 14, 2017
I should be there at the start but will need to travel during part of the meeting as well so my participation may be spotty.
joshgav commentedon Feb 15, 2017
I'm traveling tomorrow and won't be able to make it. Can someone else please take notes? Thanks!
Trott commentedon Feb 15, 2017
I'll be missing most or all of the meeting, and it's 3AM for Rod, so he's missing it to almost certainly. It's a pretty slim agenda right now. Two of the three issues that are on the agenda were put there by @jasnell. Maybe he can run the meeting? And hopefully someone volunteers to take notes...
bnoordhuis commentedon Feb 15, 2017
Perhaps we should skip it? There seems to be consensus on nodejs/node#10467, nodejs/TSC#174 has no significant new developments, and I don't think we're remotely ready to discuss nodejs/node#11233, never mind reaching a decision.
Speaking for myself, I haven't even seriously started reading through all the discussion threads, let alone form a well-reasoned opinion.
cjihrig commentedon Feb 15, 2017
I am unable to attend this week.
jasnell commentedon Feb 15, 2017
I'm good with skipping. I know quite a few folks are tied up this week.
evanlucas commentedon Feb 15, 2017
+1 to skipping
Fishrock123 commentedon Feb 15, 2017
Decided on the call to skip this week. Agenda is sparse and nothing is too pressing this week.