Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Node.js Foundation Technical Steering Committee (TSC) Meeting 2019-07-31 #738

Closed
mhdawson opened this issue Jul 29, 2019 · 8 comments
Closed
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Jul 29, 2019

Time

UTC Wed 31-Jul-2019 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Wed 31-Jul-2019 09:00 (09:00 AM)
US / Mountain Wed 31-Jul-2019 10:00 (10:00 AM)
US / Central Wed 31-Jul-2019 11:00 (11:00 AM)
US / Eastern Wed 31-Jul-2019 12:00 (12:00 PM)
London Wed 31-Jul-2019 17:00 (05:00 PM)
Amsterdam Wed 31-Jul-2019 18:00 (06:00 PM)
Moscow Wed 31-Jul-2019 19:00 (07:00 PM)
Chennai Wed 31-Jul-2019 21:30 (09:30 PM)
Hangzhou Thu 01-Aug-2019 00:00 (12:00 AM)
Tokyo Thu 01-Aug-2019 01:00 (01:00 AM)
Sydney Thu 01-Aug-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

  • process: improve nextTick performance #25461
  • buffer: add Buffer.harden() method 28439

nodejs/TSC

  • Nominating @BethGriggs to the TSC #718
  • Tracking issue for updating TSC on Board Meetings #476
  • Strategic Initiatives - Tracking Issue #423

Invited

Observers/Guests

Beth Griggs @BethGriggs (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 Jul 29, 2019
@ChALkeR
Copy link
Member

ChALkeR commented Jul 29, 2019

@mhdawson Given that the agenda is almost clear, could we add nodejs/node#28439 to the list? I just labelled it.

@Trott
Copy link
Member

Trott commented Jul 29, 2019

@apapirovski Are you able to make this week's meeting and be prepared to talk about nodejs/node#25461?

@mhdawson
Copy link
Member Author

@ChALkeR added.

@apapirovski
Copy link
Member

@Trott yep but I don’t have much to add beyond what was in the issue. There’s a fundamental breakage of the expectations that come with using async hooks when two different objects are used...

@huyf2018

This comment has been minimized.

@mhdawson
Copy link
Member Author

@apapirovski I think in part we need a response to nodejs/node#25461 (comment)

@Fishrock123
Copy link
Contributor

@huyf2018 Please ask on https://github.com/nodejs/help

@mhdawson
Copy link
Member Author

PR for minutes: #739

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

No branches or pull requests

6 participants