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 Foundation Technical Steering Committee (TSC) Meeting 2019-09-18 #755

Closed
mhdawson opened this issue Sep 16, 2019 · 4 comments
Closed
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Wed 18-Sep-2019 20:00 (08:00 PM):

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

  • src,lib: make ^C print a JS stack trace #29207
  • stream: don't emit error after destroy() #29197
  • build: ongoing list of actions for Python 3 compatibility #25789

nodejs/admin

  • Moderation team recertification #408

Invited

Observers/Guests

  • Christian Clauss @cclauss (guest participant)

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 Sep 16, 2019
@sam-github
Copy link
Contributor

Is it too late to add nodejs/node#29493 (comment) to the agenda?

@Trott
Copy link
Member

Trott commented Sep 17, 2019

I can't make it this week, but it seems like we should be able to close the loop on Moderation Team recertification. Based on what I'm seeing in the issue, it seems like we should re-certify the following people:

We should not re-certify these people as they have voluntarily removed themselves from the team or have not responded, but can always be added at a later time if they decide they want to be part of the team:

(@ryanmurakami If you could do the documented offboarding steps for those two, that's probably appropriate at this time.)

There is definitely room for more people on the Moderation Team, and also more diversity. Nominations/volunteers should likely be solicited.

@addaleax
Copy link
Member

nodejs/node#29589 was also added to the agenda somewhat late, I've added a tl;dr that I hope is pretty accurate at the end of the thread.

@Trott
Copy link
Member

Trott commented Sep 18, 2019

Minutes PR is at #756 so closing this issue.

@Trott Trott closed this as completed Sep 18, 2019
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