Skip to content

Node.js Technical Steering Committee (TSC) Meeting 2020-06-04 #873

Closed

Description

@mhdawson

Time

UTC Thu 04-Jun-2020 20:00 (08:00 PM):

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

  • lib: initial experimental AbortController implementation #33527
  • url: remove gopher from special schemes #33325
  • bootstrap: include bootstrapped Environment in builtin snapshot #32984

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 Jun 1, 2020
  2. mcollina commented on Jun 1, 2020

    @mcollina
    SponsorMember

    Too late for me

  3. Trott commented on Jun 4, 2020

    @Trott
    Member

    Moderation Team report:

    I should note that I don't think the Gitter is official and is not actually bound by our CoC, but since it was reported by and handled by a Moderation team member, I'm reporting it here anyway.

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

  4. joyeecheung commented on Jun 4, 2020

    @joyeecheung
    Member
  5. sam-github commented on Jun 4, 2020

    @sam-github
    Contributor

    Just as a heads up, I'll be on vacation for the next 2 weeks, with limited time for reviewing gh notifications.

  6. joyeecheung commented on Jun 4, 2020

    @joyeecheung
    Member

    @jasnell About the agenda item, since we keep missing each other in the meetings, maybe it would be better if we just open an issue in the TSC repo to discuss the process change asynchronously? Since you mentioned that you are interested in championing the process discussion, do you want to open an issue and elaborate on that? Or I can do it if you'd like.

  7. Trott commented on Jun 4, 2020

    @Trott
    Member

    Did the meeting happen and ended already? Or did it get canceled? I tried to join and it said it hadn't started yet, which makes me suspect it actually already ended?

  8. jasnell commented on Jun 4, 2020

    @jasnell
    Member

    Yeah, that works. I'm fairly tied up right now which is why I couldn't make the call today. If you could open the issue to kick it off that would be very helpful and I will jump in. realistically though it likely won't be until next week at the earliest.

  9. tniessen commented on Jun 4, 2020

    @tniessen
    Member

    @Trott It ended :)

  10. mhdawson commented on Jun 4, 2020

    @mhdawson
    MemberAuthor

    PR for minutes: #874

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