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-02-12 #815

Closed
mhdawson opened this issue Feb 10, 2020 · 13 comments
Closed

Node.js Technical Steering Committee (TSC) Meeting 2020-02-12 #815

mhdawson opened this issue Feb 10, 2020 · 13 comments
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Feb 10, 2020

Time

UTC Wed 12-Feb-2020 20:00 (08:00 PM):

Timezone Date/Time
US / Pacific Wed 12-Feb-2020 12:00 (12:00 PM)
US / Mountain Wed 12-Feb-2020 13:00 (01:00 PM)
US / Central Wed 12-Feb-2020 14:00 (02:00 PM)
US / Eastern Wed 12-Feb-2020 15:00 (03:00 PM)
London Wed 12-Feb-2020 20:00 (08:00 PM)
Amsterdam Wed 12-Feb-2020 21:00 (09:00 PM)
Moscow Wed 12-Feb-2020 23:00 (11:00 PM)
Chennai Thu 13-Feb-2020 01:30 (01:30 AM)
Hangzhou Thu 13-Feb-2020 04:00 (04:00 AM)
Tokyo Thu 13-Feb-2020 05:00 (05:00 AM)
Sydney Thu 13-Feb-2020 07:00 (07: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: remove duplicate env field from CryptoJob #31588
  • doc: add example for cipher.update() #28373

nodejs/TSC

  • Node.js future directions - any interest in online or in person summit? #797

nodejs/admin

  • Node.js Social Media Accounts #454

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 Feb 10, 2020
@jasnell
Copy link
Member

jasnell commented Feb 10, 2020

Both #28373 and #31588 have been previously discussed, correct? Is there reason for both to still be on the agenda or has the label just not been removed for those?

@jasnell
Copy link
Member

jasnell commented Feb 10, 2020

I'll have an update on some QUIC-related OpenSSL issues for the strategic initiatives section.

@addaleax
Copy link
Member

Both #28373 and #31588 have been previously discussed, correct? Is there reason for both to still be on the agenda or has the label just not been removed for those?

There hasn’t been any further movement on those since the meeting, so I’ll go remove the labels. If there’s more, we can always add them back.

@MylesBorins
Copy link
Contributor

It seems like there is a conflict between the TSC meeting and the Modules team meeting. I just noticed, I unfortunately had the wrong time on my calendar. Not sure what we could do to rectify this last minute

@ChALkeR
Copy link
Member

ChALkeR commented Feb 12, 2020

I can't join the meeting for some reason.

@ChALkeR
Copy link
Member

ChALkeR commented Feb 12, 2020

Ah, what @MylesBorins said.
Perhaps we cancel and review the meeting times before the next conflict (in 3 weeks, as I understand)?
Neither #31588 nor #28373 have the label anymore.

@sam-github
Copy link
Contributor

I don't think the meeting has been started yet.

@mhdawson
Copy link
Member Author

There is a conflict with the modules meeting. Normally I would have caught it and switched in advance but just got back today.

Looking at the agenda for today I don't see anything urgent so unless there are objections lets just cancel for this week.

Any objections?

Sorry for the late notice.

@mhdawson
Copy link
Member Author

Given that we have open as well around looking at meeting times: #809.

can everybody update their availability in the spreadsheet (I'll send out link via email) and then we'll review the meeting times.

@MylesBorins
Copy link
Contributor

MylesBorins commented Feb 12, 2020

The modules team is happy to end at 12:30 to share the timeslot. Please lmk if anyone would want to do this.

@sam-github
Copy link
Contributor

I think we should just cancel, there is nothing on the agenda we can't discuss perfectly well next week.

@mhdawson
Copy link
Member Author

Closing

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

6 participants