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-15 #79

Closed
Trott opened this issue Mar 13, 2017 · 9 comments
Closed

Node.js Foundation Core Technical Committee (CTC) Meeting 2017-03-15 #79

Trott opened this issue Mar 13, 2017 · 9 comments

Comments

@Trott
Copy link
Member

Trott commented Mar 13, 2017

Time

UTC Wed 15-Mar-2017 20:00 (08:00 PM):

Timezone Date/Time
US / Pacific Wed 15-Mar-2017 13:00 (01:00 PM)
US / Mountain Wed 15-Mar-2017 14:00 (02:00 PM)
US / Central Wed 15-Mar-2017 15:00 (03:00 PM)
US / Eastern Wed 15-Mar-2017 16:00 (04:00 PM)
Amsterdam Wed 15-Mar-2017 21:00 (09:00 PM)
Moscow Wed 15-Mar-2017 23:00 (11:00 PM)
Chennai Thu 16-Mar-2017 01:30 (01:30 AM)
Tokyo Thu 16-Mar-2017 05:00 (05:00 AM)
Sydney Thu 16-Mar-2017 07:00 (07: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

  • Symbol key props visible in inspection by default #9726

nodejs/TSC

  • Updating the Copyright #174

nodejs/node-eps

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

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 13, 2017

Note that this one is scheduled to be up voted on if there is no resolution in the GitHub issue (which it looks like there won't be): "Symbol key props visible in inspection by default" nodejs/node#9726

@Trott
Copy link
Member Author

Trott commented Mar 13, 2017

@bmeck Does nodejs/node-eps#51 "002 - web compat of file extension/index searching" need to be on the agenda again this meeting? Or is it just leftover from last time and I can remove the label for now?

@Trott
Copy link
Member Author

Trott commented Mar 13, 2017

Items labeled for ctc-review, PTAL:

@Trott
Copy link
Member Author

Trott commented Mar 13, 2017

Is it time to move "buffer: discuss future direction of Buffer constructor API" nodejs/node#9531 from ctc-review to ctc-agenda and hopefully come to a decision about what we are and aren't doing there?

@addaleax
Copy link
Member

Is it time to move "buffer: discuss future direction of Buffer constructor API" nodejs/node#9531 from ctc-review to ctc-agenda and hopefully come to a decision about what we are and aren't doing there?

If we have the time for it, that might make sense.

@bnoordhuis
Copy link
Member

Probably can't join tomorrow, social obligations. I'll chime in on the tagged issues.

@MylesBorins
Copy link

likely won't be able to make it tomorrow, will chime in on issues

@MylesBorins
Copy link

Can y'all please bring up #67 and make sure that everyone is aware of the upcoming TC39 + CTC dinner?

@joshgav
Copy link
Contributor

joshgav commented Mar 15, 2017

notes in #80

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

5 participants