Skip to content

Node.js Foundation Technical Steering Committee (TSC) Meeting 2018-01-24 #475

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
mhdawson opened this issue Jan 22, 2018 · 7 comments
Closed
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Wed 24-Jan-2018 12:00 (12:00 PM):

Timezone Date/Time
US / Pacific Wed 24-Jan-2018 04:00 (04:00 AM)
US / Mountain Wed 24-Jan-2018 05:00 (05:00 AM)
US / Central Wed 24-Jan-2018 06:00 (06:00 AM)
US / Eastern Wed 24-Jan-2018 07:00 (07:00 AM)
London Wed 24-Jan-2018 12:00 (12:00 PM)
Amsterdam Wed 24-Jan-2018 13:00 (01:00 PM)
Moscow Wed 24-Jan-2018 15:00 (03:00 PM)
Chennai Wed 24-Jan-2018 17:30 (05:30 PM)
Hangzhou Wed 24-Jan-2018 20:00 (08:00 PM)
Tokyo Wed 24-Jan-2018 21:00 (09:00 PM)
Sydney Wed 24-Jan-2018 23:00 (11:00 PM)

Or in your local time:

Links

Agenda

Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/node

  • esm: provide named exports for all builtin libraries #18131
  • configure: fix type of arm_version #14595

nodejs/benchmarking

  • Setup bluebird and/or wikipedia benchmarks for promise performance #188

nodejs/TSC

  • Strategic Initiatives - Tracking Issue #423

Invited

Observers

Notes

The agenda comes from issues labelled with tsc-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 TSC that's not worth putting on as a separate agenda item, this is a good place for that

@mhdawson mhdawson self-assigned this Jan 22, 2018
@mcollina
Copy link
Member

I might (or might not) be able to join - I'll be landing in Singapore that day. Timezone is friendly.

@fhinkel
Copy link
Member

fhinkel commented Jan 23, 2018

Is anybody joining tomorrow who can stream the meeting?

@danbev
Copy link
Contributor

danbev commented Jan 24, 2018

Sorry, I won't be able to attend todays meeting (still home taking care of sick kid).

@Trott
Copy link
Member

Trott commented Jan 24, 2018

I will try to wake up for it, but am likely to skip. (If I do attend, I will be unable to speak but will be able to do the usual typing into the chat.)

@targos
Copy link
Member

targos commented Jan 24, 2018

I will be joining, but cannot stream

@ChALkeR
Copy link
Member

ChALkeR commented Jan 24, 2018

Sorry, I will miss the meeting today, got a time conflict.

@fhinkel
Copy link
Member

fhinkel commented Jan 24, 2018

We ended up cancelling today due to low participation. Closing.
If you could look at nodejs/node#14595 so it can get a second lgtm, that would be great.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

7 participants