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 Technical Steering Committee (TSC) Meeting 2020-06-04 #873

Closed
mhdawson opened this issue Jun 1, 2020 · 9 comments
Closed

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

mhdawson opened this issue Jun 1, 2020 · 9 comments
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Jun 1, 2020

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
@mhdawson mhdawson self-assigned this Jun 1, 2020
@mcollina
Copy link
Member

mcollina commented Jun 1, 2020

Too late for me

@Trott
Copy link
Member

Trott commented Jun 4, 2020

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

@joyeecheung
Copy link
Member

Startup Performance:

@sam-github
Copy link
Contributor

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

@joyeecheung
Copy link
Member

joyeecheung commented Jun 4, 2020

@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.

@Trott
Copy link
Member

Trott commented Jun 4, 2020

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?

@jasnell
Copy link
Member

jasnell commented Jun 4, 2020

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.

@tniessen
Copy link
Member

tniessen commented Jun 4, 2020

@Trott It ended :)

@mhdawson
Copy link
Member Author

mhdawson commented Jun 4, 2020

PR for minutes: #874

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

7 participants