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 2016-11-23 #35
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.
Sorry about the error. Always feel free to fix something and leave a comment. I'm sure it won't be the last time I mess something up in one of these.
Only one item on the agenda so far, but it's a big one that's worth taking the time to form an opinion on. In addition to the PR linked in the agenda, there's also nodejs/node#9531 and the private conversation on the CTC mailing list.
It's a lot to catch up on if you haven't been keeping up. But it's important. At the very least, the PR in question is something we should come to resolution on sooner rather than later.
@bnoordhuis It's not exactly a short summary, but I think one can get a reasonable idea of the state of things (at least as far as the public discussion goes) by starting with @mcollina's comment at nodejs/node#9531 (comment) and reading on from there.
Activity
thefourtheye commentedon Nov 21, 2016
@Trott The local time links refer to the last week's time.
ChALkeR commentedon Nov 21, 2016
@thefourtheye Fixed, thanks!
Trott commentedon Nov 21, 2016
Sorry about the error. Always feel free to fix something and leave a comment. I'm sure it won't be the last time I mess something up in one of these.
Only one item on the agenda so far, but it's a big one that's worth taking the time to form an opinion on. In addition to the PR linked in the agenda, there's also nodejs/node#9531 and the private conversation on the CTC mailing list.
It's a lot to catch up on if you haven't been keeping up. But it's important. At the very least, the PR in question is something we should come to resolution on sooner rather than later.
bnoordhuis commentedon Nov 21, 2016
Can someone post a short summary of the Buffer discussions? I kind of lost track.
joshgav commentedon Nov 21, 2016
@bnoordhuis, FWIW here are the CTC discussions from August:
Trott commentedon Nov 21, 2016
@bnoordhuis It's not exactly a short summary, but I think one can get a reasonable idea of the state of things (at least as far as the public discussion goes) by starting with @mcollina's comment at nodejs/node#9531 (comment) and reading on from there.
ChALkeR commentedon Nov 23, 2016
I will probably be about 5 minutes late today.
joshgav commentedon Nov 28, 2016
Notes landed, closing this issue.