Skip to content

Node.js Technical Steering Committee (TSC) Meeting 2020-09-03 #915

Closed

Description

@mhdawson

Time

UTC Thu 03-Sep-2020 15:00 (03:00 PM):

Timezone Date/Time
US / Pacific Thu 03-Sep-2020 08:00 (08:00 AM)
US / Mountain Thu 03-Sep-2020 09:00 (09:00 AM)
US / Central Thu 03-Sep-2020 10:00 (10:00 AM)
US / Eastern Thu 03-Sep-2020 11:00 (11:00 AM)
London Thu 03-Sep-2020 16:00 (04:00 PM)
Amsterdam Thu 03-Sep-2020 17:00 (05:00 PM)
Moscow Thu 03-Sep-2020 18:00 (06:00 PM)
Chennai Thu 03-Sep-2020 20:30 (08:30 PM)
Hangzhou Thu 03-Sep-2020 23:00 (11:00 PM)
Tokyo Fri 04-Sep-2020 00:00 (12:00 AM)
Sydney Fri 04-Sep-2020 01:00 (01: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

  • [v14.x backport] stream: simpler and faster Readable async iterator #34887
  • Rename default branch from "master" to "main" or something similar #33864
  • process: Change default --unhandled-rejections=throw #33021
    • Voting on the default behavior for Promise unhandled rejections #916

nodejs/nodejs.org

  • blm: convert to button #3306

nodejs/TSC

  • Package manager manager ... discussion #904

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 Aug 31, 2020
  2. mmarchini commented on Sep 1, 2020

    @mmarchini
    Contributor

    heads up, I added this to the agenda: #916

  3. mcollina commented on Sep 1, 2020

    @mcollina
    SponsorMember

    I won't be able to join to discuss #34887. Maybe you can invite @ronag.

  4. ronag commented on Sep 1, 2020

    @ronag
    Member

    I'm happy to participate but I'm not sure what further input I can provide in relation to the last time I was invited?

    I think @MylesBorins and a few others expressed positive feedback on landing it but wanted further feedback from collaborators. If there is someone particular we would like to receive feedback from I would encourage a ping or two on the PR. I've requested a review from @benjamingr who did a deep review of the original PR.

  5. mhdawson commented on Sep 1, 2020

    @mhdawson
    MemberAuthor

    @ronag should #34887 still be on the agenda, I had thought we'd agreed it could be removed until more input was needed?

  6. mhdawson commented on Sep 1, 2020

    @mhdawson
    MemberAuthor

    @jasnell, should #904 still be on the agenda ?

  7. ronag commented on Sep 2, 2020

    @ronag
    Member

    @ronag should #34887 still be on the agenda, I had thought we'd agreed it could be removed until more input was needed?

    Not sure. It wasn't me that added it to the agenda. As it looks right know nothing is happening with it... So I guess one thing to discuss is whether there has been sufficient collab feedback and if not how that could be achieved.

  8. Trott commented on Sep 3, 2020

    @Trott
    Member

    Moderation Team Report:

    Blocked bot-like spam PR user. https://github.com/nodejs/moderation/issues/375

    No other Moderation Team activity to report.

    @nodejs/moderation @nodejs/tsc @nodejs/community-committee

  9. jasnell commented on Sep 3, 2020

    @jasnell
    Member

    I believe that #904 can be taken off the agenda now. The discussion is progressing on GitHub.

  10. mhdawson commented on Sep 3, 2020

    @mhdawson
    MemberAuthor

    PR for minutes: #918

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