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 2021-01-14 #963

Closed
mhdawson opened this issue Jan 11, 2021 · 11 comments
Closed

Node.js Technical Steering Committee (TSC) Meeting 2021-01-14 #963

mhdawson opened this issue Jan 11, 2021 · 11 comments
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Thu 14-Jan-2021 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Thu 14-Jan-2021 08:00 (08:00 AM)
US / Mountain Thu 14-Jan-2021 09:00 (09:00 AM)
US / Central Thu 14-Jan-2021 10:00 (10:00 AM)
US / Eastern Thu 14-Jan-2021 11:00 (11:00 AM)
EU / Western Thu 14-Jan-2021 16:00 (04:00 PM)
EU / Central Thu 14-Jan-2021 17:00 (05:00 PM)
EU / Eastern Thu 14-Jan-2021 18:00 (06:00 PM)
Moscow Thu 14-Jan-2021 19:00 (07:00 PM)
Chennai Thu 14-Jan-2021 21:30 (09:30 PM)
Hangzhou Fri 15-Jan-2021 00:00 (12:00 AM)
Tokyo Fri 15-Jan-2021 01:00 (01:00 AM)
Sydney Fri 15-Jan-2021 03:00 (03: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

  • Nominating Milad as a Node.js collaborator #36570
  • Nominating Xu Meng as as Node.js collaborator #36569
  • http: replace destroySoon with socket.end #36205
  • TLS: improve compliance with shutdown standard, remove hacks #36111
  • Rename default branch from "master" to "main" or something similar #33864

nodejs/docker-node

  • Publish packages to GitHub Registry #1410

nodejs/admin

  • Audit Google account access #389

nodejs/security-wg

  • Potential stagnation of open issues on h1 bounty program #654

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 Jan 11, 2021
@Trott
Copy link
Member

Trott commented Jan 12, 2021

@mmarchini
Copy link
Contributor

mmarchini commented Jan 12, 2021

Can we remove nodejs/node#33864 and nodejs/admin#389 from the agenda if we don't have nothing to discuss about those this week, and re-add when we have things to discuss? We've been rolling those over for months now.

@mhdawson
Copy link
Member Author

mhdawson commented Jan 13, 2021

In terms of nodejs/admin#389 I've just emailed Tierney a list to remove so lets leave on so that we close, otherwise I don't think it will ever happen

In terms of nodejs/node#33864 I've heard that GitHub is going to have some new features soon to help with the transition so might be best to have Myles comment on removing in the meeting this week.

@ljharb
Copy link
Member

ljharb commented Jan 13, 2021

Github landed those features last week; so it might be time to do the rename.

@targos
Copy link
Member

targos commented Jan 13, 2021

Github landed those features last week; so it might be time to do the rename.

Did they communicate about it? I couldn't find anything on the GitHub blog.

@ljharb
Copy link
Member

ljharb commented Jan 13, 2021

Nope, I’ve seen no announcement yet, but https://twitter.com/ljharb/status/1348718520113061888?s=21

@targos
Copy link
Member

targos commented Jan 14, 2021

I have another meeting today at work that I cannot miss.

@jasnell
Copy link
Member

jasnell commented Jan 14, 2021

Unfortunately I won't be able to make today due to company meeting conflicts. I'll try to get time to weigh in on the various items on the agenda later in the day. +1 to the various new contributor nominations

@tniessen
Copy link
Member

I am still in another meeting and will join a little later.

@panva
Copy link
Member

panva commented Jan 15, 2021

Github landed those features last week; so it might be time to do the rename.

Did they communicate about it? I couldn't find anything on the GitHub blog.

https://github.com/github/renaming#renaming-existing-branches

@mhdawson
Copy link
Member Author

PR for minutes: #964

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

8 participants