Skip to content

Node.js Technical Steering Committee (TSC) Meeting 2022-03-16 #1186

Closed

Description

@mhdawson

Time

UTC Wed 16-Mar-2022 11:00 (11:00 AM):

Timezone Date/Time
US / Pacific Wed 16-Mar-2022 04:00 (04:00 AM)
US / Mountain Wed 16-Mar-2022 05:00 (05:00 AM)
US / Central Wed 16-Mar-2022 06:00 (06:00 AM)
US / Eastern Wed 16-Mar-2022 07:00 (07:00 AM)
EU / Western Wed 16-Mar-2022 11:00 (11:00 AM)
EU / Central Wed 16-Mar-2022 12:00 (12:00 PM)
EU / Eastern Wed 16-Mar-2022 13:00 (01:00 PM)
Moscow Wed 16-Mar-2022 14:00 (02:00 PM)
Chennai Wed 16-Mar-2022 16:30 (04:30 PM)
Hangzhou Wed 16-Mar-2022 19:00 (07:00 PM)
Tokyo Wed 16-Mar-2022 20:00 (08:00 PM)
Sydney Wed 16-Mar-2022 22:00 (10:00 PM)

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

  • Add a resume-ci label to issues? #40817
  • Rename default branch from "master" to "main" #33864

nodejs/TSC

  • Publishing specs for Buffer and EventEmitter #1176

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.


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 Mar 14, 2022
  2. mcollina commented on Mar 14, 2022

    @mcollina
    SponsorMember

    I can chair if somebody shares the password to start the streaming with me.

  3. cjihrig commented on Mar 14, 2022

    @cjihrig
    Contributor

    Proposal: Adding a built-in test runner nodejs/node#40954

    This can be removed from the agenda. I've removed the tsc-agenda label from the issue.

  4. Trott commented on Mar 14, 2022

    @Trott
    Member

    Daylight savings time has started in most of the U.S., much of Canada, and many other places. And it starts in much of Europe in about two weeks. So it's probably a good time for everyone on the TSC to confirm/update their availability in the availability spreadsheet. Send me an email if you need the link. @nodejs/tsc

  5. mhdawson commented on Mar 14, 2022

    @mhdawson
    MemberAuthor

    @brianwarner can you give @mcollina access to the zoom password?

    @mcollina I'm also adding you to the zoom email in case you need an authentication code.- nodejs/email#185

  6. mhdawson commented on Mar 14, 2022

    @mhdawson
    MemberAuthor

    @mcollina thanks for chairing.

  7. brianwarner commented on Mar 14, 2022

    @brianwarner

    @mcollina I've shared the creds with you.

  8. mcollina commented on Mar 15, 2022

    @mcollina
    SponsorMember

    @mcollina I've shared the creds with you.

    Unfortunately I had to reset my lastpass account - could you reshare?

  9. Trott commented on Mar 15, 2022

    @Trott
    Member
    • nominating aduh95 as a Moderation Team member #1182

    This can be taken off the agenda.

  10. targos commented on Mar 16, 2022

    @targos
    Member

    Did the meeting time change for everyone because of DST in US? I'm surprised because I don't remember being ever invited at 12:00

  11. ronag commented on Mar 16, 2022

    @ronag
    Member

    Is there a meeting? It's 12 PM CET now.

  12. joyeecheung commented on Mar 16, 2022

    @joyeecheung
    Member

    Startup performance updates:

  13. tniessen commented on Mar 16, 2022

    @tniessen
    Member

    I don't have creds to start the meeting... given the agenda, I suggest we cancel.

  14. mcollina commented on Mar 16, 2022

    @mcollina
    SponsorMember

    I have, just a sec

  15. mcollina commented on Mar 16, 2022

    @mcollina
    SponsorMember

    I'm currently having an argument with zoom, just a sec.

  16. 2 remaining items

  17. aduh95 commented on Mar 16, 2022

    @aduh95
    Contributor

    I suggest we cancel, the agenda is pretty light anyway.

  18. mcollina commented on Mar 16, 2022

    @mcollina
    SponsorMember

    If you want we can use my zoom room or we can cancel.

  19. ronag commented on Mar 16, 2022

    @ronag
    Member

    I'm ok with cancel.

  20. tniessen commented on Mar 16, 2022

    @tniessen
    Member

    nodejs/node#40817 and #1176 can probably both be discussed in the respective issues first. +1 to cancel

  21. RaisinTen commented on Mar 16, 2022

    @RaisinTen
    Member

    +1 about cancelling.

  22. richardlau commented on Mar 16, 2022

    @richardlau
    Member

    I'm also okay with cancelling.

  23. gireeshpunathil commented on Mar 16, 2022

    @gireeshpunathil
    Member

    +1 to cancel

  24. mcollina commented on Mar 16, 2022

    @mcollina
    SponsorMember

    Canceled.

    However I would really like to understand why I couldn't promote anyone as panelist while being the host.

  25. Trott commented on Mar 16, 2022

    @Trott
    Member

    Since it wasn't canceled until the start time, we should probably have minutes opened that doesn't do anything other than list the attendees. Gotta make sure we appease find-inactive-tsc.mjs.

  26. reopened this on Mar 16, 2022
  27. Trott commented on Mar 16, 2022

    @Trott
    Member

    I (or anyone else) can open a minutes PR but I'd need to know who was there. I'm not sure how to collect those names other than maybe self-reporting. Any ideas?

  28. mcollina commented on Mar 16, 2022

    @mcollina
    SponsorMember

    I was unable to promote anybody to the zoom, so technically there were no attendees.

  29. mhdawson commented on Jun 28, 2022

    @mhdawson
    MemberAuthor

    Goint to close since there was no meeting, no next step as far as I can tell.

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