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-11-20 #777

Closed
mhdawson opened this issue Nov 18, 2019 · 5 comments
Closed
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Wed 20-Nov-2019 15:00 (03:00 PM):

Timezone Date/Time
US / Pacific Wed 20-Nov-2019 07:00 (07:00 AM)
US / Mountain Wed 20-Nov-2019 08:00 (08:00 AM)
US / Central Wed 20-Nov-2019 09:00 (09:00 AM)
US / Eastern Wed 20-Nov-2019 10:00 (10:00 AM)
London Wed 20-Nov-2019 15:00 (03:00 PM)
Amsterdam Wed 20-Nov-2019 16:00 (04:00 PM)
Moscow Wed 20-Nov-2019 18:00 (06:00 PM)
Chennai Wed 20-Nov-2019 20:30 (08:30 PM)
Hangzhou Wed 20-Nov-2019 23:00 (11:00 PM)
Tokyo Thu 21-Nov-2019 00:00 (12:00 AM)
Sydney Thu 21-Nov-2019 02:00 (02: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/build

  • New strategy for managing, sharing and documenting release keys needed #1913

nodejs/node

  • macOS Installer Requires Notarization To Be Run Under Catalina and Beyond #29216

nodejs/admin

  • Collaborator Summit - Montreal 2019 #416

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

I untagged nodejs/node#29216 it was discussed last TSC.

@fivetanley
Copy link

I untagged nodejs/node#29216 it was discussed last TSC.

Hey @sam-github, pardon me if I'm reading this comment incorrectly, but it looks like the 2019-11-13 meeting was cancelled. Was this Mac OS Catalina notorization issue discussed at an earlier TSC meeting that I could catch up on for meeting notes or watching the video? If this issue wasn't cancelled, is it possible to get it back on the agenda? If my understanding is correct it currently breaks a lot of node.js based CLI installers.

@sam-github
Copy link
Contributor

Last TSC was 2019-11-06, link to minutes: https://github.com/nodejs/TSC/blob/master/meetings/2019-11-06.md#nodejsnode

@sam-github
Copy link
Contributor

And I should say:

If this issue wasn't cancelled, is it possible to get it back on the agenda?

Did you mean meeting cancelled? The issue is not cancelled.

Any collab can put things on the agenda, or ping a collaborator to make it happen, but if its on the agenda it should be clear what has to be discussed or decided. Taking off the agenda doesn't mean its not an important or outstanding issue, it just means talking about it isn't necessarily helpful to getting it resolved.

@mhdawson
Copy link
Member Author

PR for minute: #778

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

3 participants