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-01-31 #478

Closed
mhdawson opened this issue Jan 29, 2018 · 10 comments
Closed
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Jan 29, 2018

Time

UTC Wed 31-Jan-2018 17:00 (05:00 PM):

Timezone Date/Time
US / Pacific Wed 31-Jan-2018 09:00 (09:00 AM)
US / Mountain Wed 31-Jan-2018 10:00 (10:00 AM)
US / Central Wed 31-Jan-2018 11:00 (11:00 AM)
US / Eastern Wed 31-Jan-2018 12:00 (12:00 PM)
London Wed 31-Jan-2018 17:00 (05:00 PM)
Amsterdam Wed 31-Jan-2018 18:00 (06:00 PM)
Moscow Wed 31-Jan-2018 20:00 (08:00 PM)
Chennai Wed 31-Jan-2018 22:30 (10:30 PM)
Hangzhou Thu 01-Feb-2018 01:00 (01:00 AM)
Tokyo Thu 01-Feb-2018 02:00 (02:00 AM)
Sydney Thu 01-Feb-2018 04:00 (04: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: document asserts Weak(Map|Set) behavior #18248
  • src: delete proccess.env values set to undefined #18158
  • esm: provide named exports for all builtin libraries #18131
  • configure: fix type of arm_version #14595
  • src: don't abort when package.json is a directory18270

nodejs/benchmarking

  • Setup bluebird and/or wikipedia benchmarks for promise performance #188

nodejs/TSC

  • Strategic Initiatives - Tracking Issue #423

nodejs/security-wg

  • Handle HackerOne org to core triage team #103

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

Uberconference; participants should have the link & numbers, contact me if you don't.

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 Jan 29, 2018
@hashseed
Copy link
Member

A bit off-topic, but please note that there is the call with the V8 team taking place right after this TSC meeting (7:15 PM Central European Time, 10:15 AM Pacific Time). I would welcome you to join, even if two meetings back-to-back can be tiring.

@bnoordhuis
Copy link
Member

Please put nodejs/node#18270 on the agenda, it needs a TSC decision.

@mhdawson
Copy link
Member Author

@bnoordhuis added.

@MylesBorins
Copy link
Contributor

I'm unfortunately won't be able to make the meeting. I'm reviewing the issues right now.

Update regarding modules:

@joyeecheung
Copy link
Member

I am a bit unwell so will not be able to stay up this late tonight..

@Trott
Copy link
Member

Trott commented Jan 31, 2018

Moderation team update:

  • Indefinite block for one user for GitHub comment spam/likely-malware from a throwaway account.
  • Indefinitely blocked one user for GitHub comment spam. Emailed user. Will remove the block if user resolves the issue.
  • One user’s temporary block was supposed to be lifted after a week, but subsequent emails from the user suggest that they are not reforming their behavior. Moderation Team consensus is to leave the block in place indefinitely.

@jasnell
Copy link
Member

jasnell commented Jan 31, 2018

Had to miss due to an academics awards ceremony for my youngest that was far more important :-)

@gibfahn
Copy link
Member

gibfahn commented Feb 1, 2018

On holiday so will miss this one (and the next).

FWIW the use of 👍 / 👎 reactions to the issue to denote ability to attend works pretty well in Build and Release, maybe worth using in the TSC too. See e.g. nodejs/build#1096. It seems a bit odd to have to have people who can't make it comment with justifications.

@mhdawson
Copy link
Member Author

mhdawson commented Feb 1, 2018

Pull request for minutes #480

@Trott
Copy link
Member

Trott commented Feb 1, 2018

We usually close these once the PR for minutes is in, I think, so I'm going to close this. Feel free to re-open if that's a mistake.

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

9 participants