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-04-18 #520

Closed
mhdawson opened this issue Apr 16, 2018 · 9 comments
Closed
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Apr 16, 2018

Time

UTC Wed 18-Apr-2018 14:00 (02:00 PM):

Timezone Date/Time
US / Pacific Wed 18-Apr-2018 07:00 (07:00 AM)
US / Mountain Wed 18-Apr-2018 08:00 (08:00 AM)
US / Central Wed 18-Apr-2018 09:00 (09:00 AM)
US / Eastern Wed 18-Apr-2018 10:00 (10:00 AM)
London Wed 18-Apr-2018 15:00 (03:00 PM)
Amsterdam Wed 18-Apr-2018 16:00 (04:00 PM)
Moscow Wed 18-Apr-2018 17:00 (05:00 PM)
Chennai Wed 18-Apr-2018 19:30 (07:30 PM)
Hangzhou Wed 18-Apr-2018 22:00 (10:00 PM)
Tokyo Wed 18-Apr-2018 23:00 (11:00 PM)
Sydney Thu 19-Apr-2018 00:00 (12: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

  • doc: add documentation on porting from Buffer(arg) usage #19827
  • Tracking Issue for Runtime Deprecation of Buffer constructor #19079

nodejs/TSC

  • Tracking issue for updating TSC on Board Meetings #476
  • Strategic Initiatives - Tracking Issue #423

nodejs/admin

  • Add Node Slack Community to scope #49

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 Apr 16, 2018
@Trott
Copy link
Member

Trott commented Apr 16, 2018

I am unlikely to be able to make this time, so if someone else could volunteer to frame these two issues, that would be great:

Also, if @TimothyGu is going to make this meeting, I would propose adding an item to add him to the TSC at this point, if we haven't scared him away yet.

@jasnell
Copy link
Member

jasnell commented Apr 16, 2018

I would appreciate if I could get some TSC review on nodejs/node#19803. It is a semver-major because it adds a new top-level module to interface with the still experimental trace events mechanism. I'd like to get it landed in time for 10.0.0. It has sufficient sign off to land at this point but I'd like to make sure there are no objections to landing it since it introduces a new top level module.

FWIW, the top level module has been reserved in npm by @mcollina so there would be zero user land breakage by enabling this.

@TimothyGu
Copy link
Member

I will indeed be at the meeting tomorrow!

@addaleax
Copy link
Member

I likely won’t be able to make it tomorrow, or if I do, I will be late. (I know I’ve missed quite a few meetings in a row – should get better over the next weeks, though.)

I’m +1 on adding @TimothyGu, if that comes up :)

@Trott
Copy link
Member

Trott commented Apr 17, 2018

I'm +1 on adding @TimothyGu as well.

@mhdawson
Copy link
Member Author

As a note, I'll be at the meeting but @fhinkel is going to chair.

@mhdawson
Copy link
Member Author

I can cover "Add Node Slack Community to scope #49 nodejs/admin#49" unless somebody else wants to take it.

@jasnell
Copy link
Member

jasnell commented Apr 18, 2018

Had a conflicting meeting this morning and could not make it.

@Trott
Copy link
Member

Trott commented Apr 18, 2018

Moderation Team Report: One spam-ish bot-looking user was blocked. See moderation repo issue 193 for details. @nodejs/tsc @nodejs/community-committee @nodejs/moderation

mhdawson pushed a commit to nodejs/email that referenced this issue Apr 19, 2018
Refs: nodejs/TSC#520

PR-URL: #97
Refs: nodejs/TSC#520
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Ali Ijaz Sheikh <ofrobots@google.com>
Reviewed-By: Franziska Hinkelmann <franziska.hinkelmann@gmail.com>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
fhinkel added a commit that referenced this issue Apr 20, 2018
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

6 participants