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-10-08 #935

Closed
mhdawson opened this issue Oct 5, 2020 · 4 comments
Closed

Node.js Technical Steering Committee (TSC) Meeting 2020-10-08 #935

mhdawson opened this issue Oct 5, 2020 · 4 comments
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Oct 5, 2020

Time

UTC Thu 08-Oct-2020 21:00 (09:00 PM):

Timezone Date/Time
US / Pacific Thu 08-Oct-2020 14:00 (02:00 PM)
US / Mountain Thu 08-Oct-2020 15:00 (03:00 PM)
US / Central Thu 08-Oct-2020 16:00 (04:00 PM)
US / Eastern Thu 08-Oct-2020 17:00 (05:00 PM)
EU / Western Thu 08-Oct-2020 22:00 (10:00 PM)
EU / Central Thu 08-Oct-2020 23:00 (11:00 PM)
EU / Eastern Fri 09-Oct-2020 00:00 (12:00 AM)
Moscow Fri 09-Oct-2020 00:00 (12:00 AM)
Chennai Fri 09-Oct-2020 02:30 (02:30 AM)
Hangzhou Fri 09-Oct-2020 05:00 (05:00 AM)
Tokyo Fri 09-Oct-2020 06:00 (06:00 AM)
Sydney Fri 09-Oct-2020 08:00 (08: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: add EventTarget-related browser globals #35496
  • 2020-10-20, Version 15.0.0 (Current) #35014
  • Rename default branch from "master" to "main" or something similar #33864
  • fs: simplify copy operations and more cleanups #31038

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 Oct 5, 2020
@Trott
Copy link
Member

Trott commented Oct 5, 2020

Moderation team report:

Blocked user and deleted issue: https://github.com/nodejs/moderation/issues/347#issuecomment-699651964
Blocked user and deleted several comments: https://github.com/nodejs/moderation/issues/381

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

@ExE-Boss
Copy link

ExE-Boss commented Oct 6, 2020

Before this gets lost in the comment history of nodejs/node#35014, I’d like to get nodejs/node#34055 and nodejs/node#34962 into v15.0.0.


I hope we can still get nodejs/node#34055 and nodejs/node#34962 into v15.0.0, which add alias modules for util.types, path.posix and path.win32 as util/types, path/posix and path/win32 respectively.

Originally posted by @ExE-Boss in nodejs/node#35014 (comment)

@Qard
Copy link
Member

Qard commented Oct 8, 2020

I'd also like to get nodejs/node#34895 into v15, if possible.

@mhdawson
Copy link
Member Author

mhdawson commented Oct 8, 2020

PR for minutes: #937.

@ExE-Boss some discussion on your comment. They will need to land and then the Release WG agree they can go in. I think the right place to continue the discussion is in nodejs/node#35014.

@mhdawson mhdawson closed this as completed Oct 8, 2020
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

4 participants