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-08 #77

Closed
Trott opened this issue Mar 6, 2017 · 17 comments
Closed

Node.js Foundation Core Technical Committee (CTC) Meeting 2017-03-08 #77

Trott opened this issue Mar 6, 2017 · 17 comments

Comments

@Trott
Copy link
Member

Trott commented Mar 6, 2017

Time

UTC Wed 08-Mar-2017 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Wed 08-Mar-2017 08:00 (08:00 AM)
US / Mountain Wed 08-Mar-2017 09:00 (09:00 AM)
US / Central Wed 08-Mar-2017 10:00 (10:00 AM)
US / Eastern Wed 08-Mar-2017 11:00 (11:00 AM)
Amsterdam Wed 08-Mar-2017 17:00 (05:00 PM)
Moscow Wed 08-Mar-2017 19:00 (07:00 PM)
Chennai Wed 08-Mar-2017 21:30 (09:30 PM)
Tokyo Thu 09-Mar-2017 01:00 (01:00 AM)
Sydney Thu 09-Mar-2017 03:00 (03: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

  • governance: add Franziska Hinkelmann to the CTC #11488 @rvagg
  • Symbol key props visible in inspection by default #9726 @Trott

nodejs/TSC

nodejs/node-eps

  • 002 - web compat of file extension/index searching #51 @bmeck

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 Mar 6, 2017

I'd especially like to call people's attention to Symbol key props visible in inspection by default as the intention there is to call for a vote. There is an impasse after lengthy conversation. Hopefully, as many of @nodejs/ctc as possible will read over the issue, and we can vote to either accept or decline the PR.

@jasnell
Copy link
Member

jasnell commented Mar 6, 2017

I'll have an update on Friday's VM summit in Seattle.

@Trott
Copy link
Member Author

Trott commented Mar 6, 2017

@nodejs/ctc For the two items that are exceedingly likely to be brought to vote, I've added counts in the Google doc. However, I'm doing some interpretation, so please double check my work and make a change if I've messed up your vote.

@Trott
Copy link
Member Author

Trott commented Mar 6, 2017

@bmeck Regarding 002 - web compat of file extension/index searching #51: Are you looking to CTC to make a decision? Or is it mostly that CTC should be aware of the issue and the conversation?

@addaleax
Copy link
Member

addaleax commented Mar 7, 2017

Sorry, probably can’t attend this one, too.

@Trott
Copy link
Member Author

Trott commented Mar 7, 2017

I'll probably miss the first half hour.

@cjihrig
Copy link

cjihrig commented Mar 7, 2017

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

@joshgav
Copy link
Contributor

joshgav commented Mar 7, 2017

Can we decide if Node 8 will start with V8 5.7? See node#10117, specifically this comment. This decision is important for tools which work with the legacy debugger.

@misterdjules
Copy link

I won't be able to make it this time.

@bnoordhuis
Copy link
Member

@joshgav Is there a separate issue I can tag ctc-agenda?

@joshgav
Copy link
Contributor

joshgav commented Mar 7, 2017

@bnoordhuis would it be #10117?

@bnoordhuis
Copy link
Member

I was hoping for one that was specifically about the debugger. We'll just have to remember to bring it up tomorrow.

@ChALkeR
Copy link
Member

ChALkeR commented Mar 8, 2017

I would also ask everyone to take a look in advance (if you have several minutes) at the email and the google spreadsheet from me that you should have received, that will make discussing it easier.

@targos
Copy link
Member

targos commented Mar 8, 2017

I won't be able to make it.

@bnoordhuis
Copy link
Member

I'm having connection problems, I keep getting dropped from the call.

@joshgav
Copy link
Contributor

joshgav commented Mar 9, 2017

Notes in #78

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