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-03-22 #82

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

Node.js Foundation Core Technical Committee (CTC) Meeting 2017-03-22 #82

Trott opened this issue Mar 20, 2017 · 12 comments

Comments

@Trott
Copy link
Member

Trott commented Mar 20, 2017

Time

UTC Wed 22-Mar-2017 05:00 (05:00 AM):

Timezone Date/Time
US / Pacific Tue 21-Mar-2017 22:00 (10:00 PM)
US / Mountain Tue 21-Mar-2017 23:00 (11:00 PM)
US / Central Wed 22-Mar-2017 00:00 (12:00 AM)
US / Eastern Wed 22-Mar-2017 01:00 (01:00 AM)
Amsterdam Wed 22-Mar-2017 06:00 (06:00 AM)
Moscow Wed 22-Mar-2017 08:00 (08:00 AM)
Chennai Wed 22-Mar-2017 10:30 (10:30 AM)
Tokyo Wed 22-Mar-2017 14:00 (02:00 PM)
Sydney Wed 22-Mar-2017 16:00 (04: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

  • buffer: discuss future direction of Buffer constructor API #9531

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.

@cjihrig
Copy link

cjihrig commented Mar 20, 2017

I won't be able to make it. The move from midnight to 1am makes it a lot more difficult.

@Trott
Copy link
Member Author

Trott commented 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
Copy link
Member Author

Trott commented Mar 20, 2017

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.)

@cjihrig
Copy link

cjihrig commented 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
Copy link

Oh, yeah. 1am. Also won't make it. Someone else will have to stream. I'll try to remember to update the sheet.

@fhinkel
Copy link
Member

fhinkel commented Mar 20, 2017

I also won't be able to make it this week.

@addaleax
Copy link
Member

ditto, I won’t be able to be there.

@misterdjules
Copy link

I won't be able to attend.

@mhdawson
Copy link
Member

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
Copy link
Contributor

joshgav commented Mar 21, 2017

cc @jasongin re #11975

@evanlucas
Copy link

I probably won't make it tonight either

@joshgav
Copy link
Contributor

joshgav commented Mar 24, 2017

Notes in #84

@joshgav joshgav closed this as completed Mar 24, 2017
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