Skip to content

Node.js Foundation Technical Steering Committee (TSC) Meeting 2019-09-11 #753

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 Sep 9, 2019 · 5 comments
Closed
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Sep 9, 2019

Time

UTC Wed 11-Sep-2019 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Wed 11-Sep-2019 09:00 (09:00 AM)
US / Mountain Wed 11-Sep-2019 10:00 (10:00 AM)
US / Central Wed 11-Sep-2019 11:00 (11:00 AM)
US / Eastern Wed 11-Sep-2019 12:00 (12:00 PM)
London Wed 11-Sep-2019 17:00 (05:00 PM)
Amsterdam Wed 11-Sep-2019 18:00 (06:00 PM)
Moscow Wed 11-Sep-2019 19:00 (07:00 PM)
Chennai Wed 11-Sep-2019 21:30 (09:30 PM)
Hangzhou Thu 12-Sep-2019 00:00 (12:00 AM)
Tokyo Thu 12-Sep-2019 01:00 (01:00 AM)
Sydney Thu 12-Sep-2019 02:00 (02:00 AM)

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

  • deps: define OPENSSLDIR and ENGINESDIR explicitly #29455
  • OpenSSL sec releases upcoming #29445
  • src,lib: make ^C print a JS stack trace #29207
  • stream: don't emit error after destroy() #29197
  • build: ongoing list of actions for Python 3 compatibility #25789
  • http2: make compat finished match http/1 #24347

nodejs/TSC

nodejs/admin

  • Moderation team recertification #408

Invited

Observers/Guests

Beth Griggs @BethGriggs (guest participant)
Christian Clauss @cclauss (guest participant)
Tobias Nießen @tniessen (guest participant)

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

Zoom link: https://zoom.us/j/611357642
Regular password

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.


Invitees

Please use the following emoji reactions in this post to indicate your
availability.

  • 👍 - Attending
  • 👎 - Not attending
  • 😕 - Not sure yet
@mhdawson mhdawson self-assigned this Sep 9, 2019
@cclauss
Copy link

cclauss commented Sep 11, 2019

Today is a red letter day because our Travis CI tests all passed on Python 3. nodejs/node#29451 -> https://travis-ci.com/nodejs/node/builds/126947698 Thanks to all who have been involved!

We are far from done with our port to Python 3 but passing these tests is an important milestone.

The WIP PR nodejs/node#29451 is an amalgam of several different PRs that need to be upstreamed/downstreamed/sidestreamed/pairstreamed so all help is greatly appreciated.

nodejs/node#25789 is our ongoing list of todos. My sense is that nodejs/node#25878 should be reviewed and landed. nodejs/node-gyp#1844 should be fixed to pass the tests and then reviewed and landed.

Help needed on nodejs/node#29326 and nodejs/node#29415 112 days until Python 2 end of life.

@mhdawson
Copy link
Member Author

@cclauss thanks for the update, added to the minutes doc.

@mhdawson
Copy link
Member Author

@nodejs/tsc if possible it would be good to confirm the nominations for @tniessen and @BethGriggs today. I think they've been invited participated in 2-3 meetings by now.

@tniessen
Copy link
Member

I have only had a chance to participate in one meeting due to scheduling conflicts. I will join the meeting today as an observer again.

@mhdawson
Copy link
Member Author

PR for minutes: #754

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

No branches or pull requests

3 participants