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 2018-06-06 #549

Closed
mhdawson opened this issue Jun 4, 2018 · 12 comments
Closed
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Jun 4, 2018

Time

UTC Wed 06-Jun-2018 17:00 (05:00 PM):

Timezone Date/Time
US / Pacific Wed 06-Jun-2018 10:00 (10:00 AM)
US / Mountain Wed 06-Jun-2018 11:00 (11:00 AM)
US / Central Wed 06-Jun-2018 12:00 (12:00 PM)
US / Eastern Wed 06-Jun-2018 13:00 (01:00 PM)
London Wed 06-Jun-2018 18:00 (06:00 PM)
Amsterdam Wed 06-Jun-2018 19:00 (07:00 PM)
Moscow Wed 06-Jun-2018 20:00 (08:00 PM)
Chennai Wed 06-Jun-2018 22:30 (10:30 PM)
Hangzhou Thu 07-Jun-2018 01:00 (01:00 AM)
Tokyo Thu 07-Jun-2018 02:00 (02:00 AM)
Sydney Thu 07-Jun-2018 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

  • worker: initial implementation #20876
  • util: recover from maximum call stack size #20725

nodejs/TSC

  • Proposal: add all new core modules under a scope? (too late for http2) #389 [ADDITION by @Trott, since we're supposed to note when we edit another Collaborator's posts...]
  • Tracking issue for updating TSC on Board Meetings #476
  • Strategic Initiatives - Tracking Issue #423

Invited

Observers

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

@mhdawson mhdawson self-assigned this Jun 4, 2018
@Trott
Copy link
Member

Trott commented Jun 5, 2018

Adding #389. Now with mime module being proposed, I think it's a good time to consider that we might want to make a decision expeditiously (which should not be confused with "rushed" and/or "uninformed").

@ljharb
Copy link
Member

ljharb commented Jun 5, 2018

If I’m able to call in during #389, that would be great.

@Trott
Copy link
Member

Trott commented Jun 6, 2018

I know this is last-minute, but it might be good to have @BridgeAR and @mscdex on as guests for nodejs/node#20725. (If you're on @nodejs/tsc and haven't registered an opinion or intention to abstain on that one, it's worth getting educated in advance and doesn't take a whole lot of time to read through the issue conversation, so do that right now!!!!)

@mhdawson
Copy link
Member Author

mhdawson commented Jun 6, 2018

I'm + 1 for inviting @BridgeAR and @mscdex

@bmeck
Copy link
Member

bmeck commented Jun 6, 2018

I'll be listening but now have a stake in #389

@mhdawson
Copy link
Member Author

mhdawson commented Jun 6, 2018

@Trott, I know its even more last-minute but I reached out to @BridgeAR through email to see if he is available but don't see an email or other way to get @mscdex the password for the meeting if he is available. Do you have his contact info?

@richardlau
Copy link
Member

I don't think think it needs to be discussed by the TSC, but it might be an idea to mention the proposal to fold the post-mortem WG into the diagnostics WG (nodejs/post-mortem#48) as a FYI.

@addaleax
Copy link
Member

addaleax commented Jun 6, 2018

@mhdawson We have all the collaborator emails in the main nodejs/node readme, I guess that’s the best way we have available?

@Trott
Copy link
Member

Trott commented Jun 6, 2018

If he's up for participating, I'd say also invite @bmeck for module scoping part.

@Trott
Copy link
Member

Trott commented Jun 6, 2018

@richardlau That can go in the announcements portion. Thanks!

@Trott
Copy link
Member

Trott commented Jun 6, 2018

Moderation Team report: No official moderation actions this week.

@nodejs/tsc @nodejs/moderation @nodejs/community-committee

@mhdawson
Copy link
Member Author

mhdawson commented Jun 6, 2018

PR for minutes: #550

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants