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-02-07 #484

Closed
mhdawson opened this issue Feb 5, 2018 · 13 comments
Closed
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Feb 5, 2018

Time

UTC Wed 07-Feb-2018 22:00 (10:00 PM):

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

  • document asserts Weak(Map|Set) behavior #18248**
  • src: don't abort when package.json is a directory #18270
  • src: delete proccess.env values set to undefined #18158
  • esm: provide named exports for all builtin libraries #18131
  • Fix typos in the 9.2.0 changelog. #17062

nodejs/TSC

  • Strategic Initiatives - Tracking Issue #423

nodejs/node-v8

  • Upcoming changes to GYP #38

Invited

Observers

@BridgeAR
@TimothyGu

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 Feb 5, 2018
@mhdawson
Copy link
Member Author

mhdawson commented Feb 5, 2018

@BridgeAR would you be able to attend the meeting to help the discussion on doc: document asserts Weak(Map|Set) behavior #18248

@TimothyGu, would you be able to attend the meeting to help the discussion on src: delete proccess.env values set to undefined #18158

@BridgeAR
Copy link
Member

BridgeAR commented Feb 5, 2018

@mhdawson yes, I would like to attend.

@mhdawson
Copy link
Member Author

mhdawson commented Feb 5, 2018

@BridgeAR sent uberconference info through email

@TimothyGu
Copy link
Member

Unfortunately I will not be able to make it to the meeting, though an hour earlier or later would work. I hope @BridgeAR and @Fishrock123 will be able to carry through my message in nodejs/node#18158 (review) to the meeting.

@cjihrig
Copy link
Contributor

cjihrig commented Feb 5, 2018

I've removed the TSC agenda label from nodejs/security-wg#103. It can be removed from this week's agenda.

@mhdawson
Copy link
Member Author

mhdawson commented Feb 5, 2018

@cjihrig done.

@Trott
Copy link
Member

Trott commented Feb 6, 2018

I'm going to miss the first half of the meeting due to a scheduling conflict with a work meeting.

@rvagg
Copy link
Member

rvagg commented Feb 7, 2018

I thought I was going to make 1/2 of this but just had an important meeting thrown at me in this slot so I'll have to skip.

The arm_version issue can be removed, it's been closed for now. And I'm abstaining from the package.json one. Strategic initiatives OpenSSL is in progress, there's a PR in this repo but I haven't pushed anything to it since last week (although I've fixed the mentioned nits in my local copy).

@Trott
Copy link
Member

Trott commented Feb 7, 2018

My proposed solution to the package.json issue is: Land nodejs/node#18270, then land nodejs/node#18593 as a semver-major (although that one seriously needs some more reviews), and then @bmeck will open a pull request to cache negative results for main.

@bmeck is (based on my understanding of our conversations at least) on board with that approach. (It may not be their ideal, but it is acceptable.) I suspect that approach is also acceptable to @bnoordhuis although I do not have confirmation on that. Pinging @bnoordhuis.

@mhdawson
Copy link
Member Author

mhdawson commented Feb 7, 2018

Meeting will be starting soon, Francisca is just setting up youtube stream.

@Trott
Copy link
Member

Trott commented Feb 7, 2018

No significant Moderation Team activity this week.

@mhdawson
Copy link
Member Author

mhdawson commented Feb 7, 2018

PR for minutes #488

@mhdawson mhdawson closed this as completed Feb 7, 2018
@Fishrock123
Copy link
Contributor

Sorry I didn’t make it to this - I’m away from home and forgot yesterday morning. :/

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

8 participants