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-04-17 #691

Closed
mhdawson opened this issue Apr 15, 2019 · 8 comments
Closed
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Apr 15, 2019

Time

UTC Wed 17-Apr-2019 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Wed 17-Apr-2019 09:00 (09:00 AM)
US / Mountain Wed 17-Apr-2019 10:00 (10:00 AM)
US / Central Wed 17-Apr-2019 11:00 (11:00 AM)
US / Eastern Wed 17-Apr-2019 12:00 (12:00 PM)
London Wed 17-Apr-2019 17:00 (05:00 PM)
Amsterdam Wed 17-Apr-2019 18:00 (06:00 PM)
Moscow Wed 17-Apr-2019 19:00 (07:00 PM)
Chennai Wed 17-Apr-2019 21:30 (09:30 PM)
Hangzhou Thu 18-Apr-2019 00:00 (12:00 AM)
Tokyo Thu 18-Apr-2019 01:00 (01:00 AM)
Sydney Thu 18-Apr-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/TSC

  • TSC Elections Chair and CPC representative. #689
  • Tracking issue for updating TSC on Board Meetings #476
  • Strategic Initiatives - Tracking Issue #423

nodejs/security-wg

  • HackerOne's managed services #516

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 Apr 15, 2019
@Trott
Copy link
Member

Trott commented Apr 15, 2019

  • domain: error handler runs outside of its domain #26211

This was put on the agenda by @mcollina (who gave the PR an approval) because TSC needs "to discuss if a semver-major change on a deprecated API is something we would like to do."

If at all possible, I'd prefer that conversation happen in GitHub rather than in a meeting. So here we go:

While we should definitely consider the fact that an API deprecated when reviewing breaking changes to it, I think a case-by-case evaluation is fine. And I think in this case (improvement to domain), a breaking change is fine. (One could even argue that the fact that the API is deprecated makes the argument for breaking changes stronger, not weaker.)

@mcollina
Copy link
Member

@Trott we talked about it last time. So I've removed it. It is still missing one other review from TSC to land.

@Trott
Copy link
Member

Trott commented Apr 15, 2019

  • HackerOne's managed services #516

Should we invite @vdeturckheim as a guest for that issue? (For that matter, is it possible for the issue to be decided outside the meeting?)

@mcollina
Copy link
Member

Should we invite @vdeturckheim as a guest for that issue? (For that matter, is it possible for the issue to be decided outside the meeting?)

I think it is almost decided via email.

@vdeturckheim
Copy link
Member

I don't think I'd be able to say more than what has been discussed on issue indeed

@mhdawson
Copy link
Member Author

Would like to remind people to self-nominate for the TSC Chair and Node.js CPC representative roles here: #689. It will help to understand how many or few people we have interested sooner than later.

@sam-github
Copy link
Contributor

I will join this meeting as an oberver, but I need a password. Can someone irc (octetcloud) or email ([email protected]) it to me? Or am I supposed to watch on youtube? Thanks1

@mhdawson
Copy link
Member Author

Minutes for meeting: #693

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

5 participants