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-08-02 #160

Closed
Trott opened this issue Jul 31, 2017 · 5 comments
Closed

Node.js Foundation Core Technical Committee (CTC) Meeting 2017-08-02 #160

Trott opened this issue Jul 31, 2017 · 5 comments

Comments

@Trott
Copy link
Member

Trott commented Jul 31, 2017

Time

UTC Wed 02-Aug-2017 20:00 (08:00 PM):

Timezone Date/Time
US / Pacific Wed 02-Aug-2017 13:00 (01:00 PM)
US / Mountain Wed 02-Aug-2017 14:00 (02:00 PM)
US / Central Wed 02-Aug-2017 15:00 (03:00 PM)
US / Eastern Wed 02-Aug-2017 16:00 (04:00 PM)
Amsterdam Wed 02-Aug-2017 22:00 (10:00 PM)
Moscow Wed 02-Aug-2017 23:00 (11:00 PM)
Chennai Thu 03-Aug-2017 01:30 (01:30 AM)
Hangzhou Thu 03-Aug-2017 04:00 (04:00 AM)
Tokyo Thu 03-Aug-2017 05:00 (05:00 AM)
Sydney Thu 03-Aug-2017 06:00 (06:00 AM)

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

  • Cleanup _writableState and _readableState access across codebase #445

nodejs/node-eps

  • proposal: ES module resolver spec for package.json "module" property #60

Invited

Observers

  • Bradley Meck @bmeck (GoDaddy/TC39)
  • Guy Bedford @guybedford
  • Tracy Hinds @hackygolucky (Node.js Foundation Education Community Manager)
  • Josh Gavant @joshgav (Microsoft)
  • Mark Hinkle @mrhinkle (Node.js Foundation Executive Director)
  • Jenn Turner @renrutnnej (Node.js Foundation Newsletter Curator)

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 Jul 31, 2017

In addition to the two items on the agenda for this week, there are seven other issues for which @nodejs/ctc review has been requested. These will not be discussed during the meeting but CTC members are encouraged to take a look at these and weigh in as appropriate:

@mhdawson
Copy link
Member

mhdawson commented Aug 1, 2017

I'm wondering what more we need on nodejs/Release#223 in terms of reaching consensus. Its approved by 2 CTC members so far.

I'd like to set a target date for "ratification" as per https://github.com/nodejs/CTC/blob/master/WORKING_GROUPS.md in the meeting this week.

I don't see any objections in the thread at this point (I believe Jame's comments have been addressed)

How about we set the target for the next meeting ?

@addaleax
Copy link
Member

addaleax commented Aug 1, 2017

I’d like to move promises: more robust stringification to the CTC agenda; there hasn’t really been any movement for a while, it’s not an overly complicated issue and it’s something on which we should come to a conclusion at some point.

@addaleax
Copy link
Member

addaleax commented Aug 1, 2017

Also, I’ll try to make it, but I can’t promise that I’ll be there.

@jasnell
Copy link
Member

jasnell commented Aug 2, 2017

I'm unfortunately quite under the weather today. I'm going to skip to get some more rest

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

5 participants