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-01 #74

Closed
Trott opened this issue Feb 27, 2017 · 13 comments
Closed

Node.js Foundation Core Technical Committee (CTC) Meeting 2017-03-01 #74

Trott opened this issue Feb 27, 2017 · 13 comments

Comments

@Trott
Copy link
Member

Trott commented Feb 27, 2017

Time

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

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

  • tracking issue: async loader for module interop #11233

nodejs/TSC

  • Updating the Copyright #174

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 Feb 27, 2017

FYI, I just left a comment on #9276 Symbol key props visible in inspection by default that might result in it landing on the agenda this week.

@bnoordhuis
Copy link
Member

I've removed the label from nodejs/node#11200, that one was settled a couple of weeks ago.

@Trott
Copy link
Member Author

Trott commented Feb 28, 2017

Just a reminder, since some of us are still probably not quite used to this time due to the "OMG it's on Tuesday?" factor for much of North America: The CTC meeting is in less than 24 hours.

@mhdawson
Copy link
Member

I'm not going to be able to make it this week, too late for me.

@gibfahn
Copy link
Member

gibfahn commented Feb 28, 2017

@Trott Just a reminder to mention #58 (giving collaborators access to the help repo)

@MylesBorins
Copy link

MylesBorins commented Feb 28, 2017 via email

@fhinkel
Copy link
Member

fhinkel commented Mar 1, 2017

Not likely to make it.

@jasnell
Copy link
Member

jasnell commented Mar 1, 2017

For the folks who cannot make it tonight, could I ask that you leave a comment indicating your position on each of the agenda items (even if it's "no position" ... :-) ...)

@evanlucas
Copy link

I probably won't make it tonight either...

@Trott
Copy link
Member Author

Trott commented Mar 1, 2017

For the folks who cannot make it tonight, could I ask that you leave a comment indicating your position on each of the agenda items (even if it's "no position" ... :-) ...)

I think you mean the ctc-review items instead. (There's only two agenda items and neither involve CTC taking a position on something.) Regardless, yeah, if everyone could look those over, that would rock.

@Trott
Copy link
Member Author

Trott commented Mar 1, 2017

Mad props to @jasnell for taking action on a whole bunch of stale issues and PRs. 🤘 (Not really specific to CTC or the meeting, but good community stewardship certainly isn't unrelated to CTC...)

@joshgav
Copy link
Contributor

joshgav commented Mar 1, 2017

notes in #75. goodnight!

@targos targos closed this as completed Mar 1, 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

10 participants