Node.js Foundation Technical Steering Committee (TSC) Meeting 2018-02-07 #484
Comments
|
@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 |
|
@mhdawson yes, I would like to attend. |
|
@BridgeAR sent uberconference info through email |
|
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. |
|
I've removed the TSC agenda label from nodejs/security-wg#103. It can be removed from this week's agenda. |
|
@cjihrig done. |
|
I'm going to miss the first half of the meeting due to a scheduling conflict with a work meeting. |
|
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). |
|
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 @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. |
|
Meeting will be starting soon, Francisca is just setting up youtube stream. |
|
No significant Moderation Team activity this week. |
|
PR for minutes #488 |
|
Sorry I didn’t make it to this - I’m away from home and forgot yesterday morning. :/ |
Time
UTC Wed 07-Feb-2018 22:00 (10:00 PM):
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
nodejs/TSC
nodejs/node-v8
Invited
Observers
@BridgeAR
@TimothyGu
Notes
The agenda comes from issues labelled with
tsc-agendaacross 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
The text was updated successfully, but these errors were encountered: