Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

Node.js Foundation Core Technical Committee (CTC) Meeting 2017-05-24 #130

Closed
Trott opened this issue May 20, 2017 · 12 comments
Closed

Node.js Foundation Core Technical Committee (CTC) Meeting 2017-05-24 #130

Trott opened this issue May 20, 2017 · 12 comments

Comments

@Trott
Copy link
Member

Trott commented May 20, 2017

Time

UTC Wed 24-May-2017 11:00 (11:00 AM):

Timezone Date/Time
US / Pacific Wed 24-May-2017 04:00 (04:00 AM)
US / Mountain Wed 24-May-2017 05:00 (05:00 AM)
US / Central Wed 24-May-2017 06:00 (06:00 AM)
US / Eastern Wed 24-May-2017 07:00 (07:00 AM)
Amsterdam Wed 24-May-2017 13:00 (01:00 PM)
Moscow Wed 24-May-2017 14:00 (02:00 PM)
Chennai Wed 24-May-2017 16:30 (04:30 PM)
Tokyo Wed 24-May-2017 20:00 (08:00 PM)
Sydney Wed 24-May-2017 21:00 (09:00 PM)

Or in your local time:

Links

Agenda

Extracted from ctc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/node

  • http: overridable keep-alive behavior of Agent #13005 added to the agenda by @indutny

nodejs/node-eps

  • Invert dependency between core and readable-stream #49 added to the agenda by @mcollina

Invited

Notes

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.

@Trott
Copy link
Member Author

Trott commented May 20, 2017

This will be our first time trying this Europe-and-India-friendly time slot. It looks like it is also Not Completely Terrible for China, Japan, and Australia.

It's going to be 4AM local time for me. I'm going to try to get out of bed for this. But if I don't make it, someone else please run the meeting. :-D

@bnoordhuis
Copy link
Member

bnoordhuis commented May 20, 2017

I've removed the ctc-review label from issues that had it for over a month (about half of Rich's list) on the assumption that if it hasn't been reviewed by now, it won't happen in the future either.

EDIT: Crossed them out in Rich's list for your browsing pleasure.

@Fishrock123
Copy link

I don't have much to add other than the "inverted dependency" thing seems to be working for node-inspect.

@evanlucas
Copy link

I may miss this one. Apologies in advance if so.

@mcollina
Copy link
Member

There is nodejs/node#12925, it is semver-major, but we would like it to land in Node 8.

@mscdex
Copy link

mscdex commented May 24, 2017

I probably won't make it either, but as far as the readable-stream issue goes, I think I am still -1 for reasons already discussed in the EP thread (including some of @AndreasMadsen's concerns) as well as reasons I've given elsewhere in a thread in this repo IIRC (I cannot find the link at the moment but I do remember discussion before the EP happened).

@mcollina
Copy link
Member

I read the time wrong, and didn't account timezone differences. I will be on a plane while this call happens :(.

@bnoordhuis
Copy link
Member

I might be a few minutes late, overlap with my other job, Taxi Service Dad.

@jasnell
Copy link
Member

jasnell commented May 24, 2017

I'm actually in the right timezone for this one but I'm going to have to miss.

@MylesBorins
Copy link

MylesBorins commented May 24, 2017 via email

@targos
Copy link
Member

targos commented May 24, 2017

Minutes: #134

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

9 participants