Skip to content

Node.js Technical Steering Committee (TSC) Meeting 2020-05-07 #860

Closed

Description

@mhdawson

Time

UTC Thu 07-May-2020 20:00 (08:00 PM):

Timezone Date/Time
US / Pacific Thu 07-May-2020 13:00 (01:00 PM)
US / Mountain Thu 07-May-2020 14:00 (02:00 PM)
US / Central Thu 07-May-2020 15:00 (03:00 PM)
US / Eastern Thu 07-May-2020 16:00 (04:00 PM)
London Thu 07-May-2020 21:00 (09:00 PM)
Amsterdam Thu 07-May-2020 22:00 (10:00 PM)
Moscow Thu 07-May-2020 23:00 (11:00 PM)
Chennai Fri 08-May-2020 01:30 (01:30 AM)
Hangzhou Fri 08-May-2020 04:00 (04:00 AM)
Tokyo Fri 08-May-2020 05:00 (05:00 AM)
Sydney Fri 08-May-2020 06:00 (06: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

  • src,win: Replacement of unsupported versions of Windows runtime exit. #33108
  • Dispute of "block running on EOL Windows versions #31954" - Alternative Suggestion #33034
  • process: Throw exception on --unhandled-rejections=default #33021
  • http: align with stream.Writable #31818

nodejs/TSC

  • Nominations for TSC Chair - Open April 16 through 30th 2020 #851
  • Node.js future directions - any interest in online or in person summit? #797

nodejs/admin

  • Audit Google account access #389

Invited

Observers/Guests

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

Activity

  1. self-assigned this
    on May 4, 2020
  2. Trott commented on May 4, 2020

    @Trott
    Member

    Moderation Team activity: Discussions of some activities/reports, but no moderation actions taken. (@nodejs/moderation Correct me if I'm wrong!) For example, in one case, an individual self-moderated before the Moderation Team took action.

    @nodejs/tsc @nodejs/community-committee

  3. Trott commented on May 4, 2020

    @Trott
    Member

    Strategic Initiatives! Let's hear about 'em!

    Initiative Champion Links
    Modules @MylesBorins https://github.com/nodejs/modules
    Core Promise APIs @mcollina
    V8 Currency @targos
    QUIC / HTTP3 @jasnell https://github.com/nodejs/quic
    Startup performance @joyeecheung nodejs/node#17058 nodejs/node#21563
    Build resources @mhdawson nodejs/build#1154 (comment)
  4. ljharb commented on May 5, 2020

    @ljharb
  5. targos commented on May 5, 2020

    @targos
    Member

    V8 Currency:

    Working on the update to V8 8.3: nodejs/node#32831 V8 8.3 is ready to land on master. Waiting for stable upstream release.
    We have FreeBSD build errors (in freebsd-specific code) and no response from the FreeBSD team so far. Fixed upstream.

  6. Trott commented on May 5, 2020

    @Trott
  7. Trott commented on May 5, 2020

    @Trott
  8. mcollina commented on May 5, 2020

    @mcollina
    SponsorMember

    Promises:

    There are some discussion around Thenable and AsyncLocalStorage in nodejs/node#33189.
    Promise hooks (used by async_hooks) are going to get faster by nodejs/node#32891.

  9. Qard commented on May 5, 2020

    @Qard
    Member

    I'm happy to join any discussion about nodejs/node#33189, or to start a separate discussion, to explain why the current state of thenables is such an issue and to work out how to deal with the problem. It's a fairly complex issue that is not adequately solved by any of the existing "fixes" we have and the nuance and complexity makes it difficult to explain adequately in text.

  10. mmarchini commented on May 6, 2020

    @mmarchini
    Contributor

    (Sharing here for visibility)

    If you have any comments on the proposed unhandled rejection survey, please share it in the PR: #857. It would be good to move forward with the survey so we can unblock nodejs/node#33021.

  11. mhdawson commented on May 6, 2020

    @mhdawson
    MemberAuthor
    • Build resources
      • Have gotten info from one potential provider, need to sync with Robin on how to review/next steps.
  12. mhdawson commented on May 6, 2020

    @mhdawson
    MemberAuthor

    @mcollina do you think we should discuss nodejs/node#33189 in the meeting and invite @Qard ?

  13. mcollina commented on May 6, 2020

    @mcollina
    SponsorMember

    I think the discussion is progressing on the issue. I only posted it here because @Trott asked for an update.

  14. jasnell commented on May 6, 2020

    @jasnell
    Member

    QUIC update: There is no update this week. Work progress on separating bits out that can be separated out.

  15. jasnell commented on May 6, 2020

    @jasnell
    Member

    And just a heads up, there is private business to discuss.

  16. BridgeAR commented on May 7, 2020

    @BridgeAR
    Member

    I am going to be a bit late.

  17. mhdawson commented on May 11, 2020

    @mhdawson
    MemberAuthor

    PR for minutes #862

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions