Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Node.js Foundation Technical Steering Committee (TSC) Meeting 2017-09-13 #338

Closed
mhdawson opened this issue Sep 8, 2017 · 12 comments
Closed

Comments

@mhdawson
Copy link
Member

mhdawson commented Sep 8, 2017

Time

UTC Wed 13-Sep-2017 20:00 (08:00 PM):

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

  • stream: remove {writeableState/readableState}.length #12857
  • Cleanup _writableState and _readableState access across codebase #445

nodejs/TSC

  • New TSC Director/Chair Elections #326
  • TSC Meeting Schedule #336
  • 2FA for the entire org #301
  • Candidate "areas" for TSC and Community Committee #278
  • Copyright Date #195
  • Regular roll-up reporting for active working groups #109

nodejs/security-wg

  • CVE management process for Node.js #33

nodejs/CTC

  • Requesting Rod to step down or be removed from the CTC #165

Invited

Observers

  • Bradley Meck @bmeck (GoDaddy/TC39)
  • Tracy Hinds @hackygolucky (Node.js Foundation Education Community Manager)
  • Kaitlyn Barnard @kbarnard10 (Node.js Foundation Newsletter Curator)
  • Mark Hinkle @mrhinkle (Node.js Foundation Executive Director)
  • William Kapke @williamkapke (Node.js Community Board representative)

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 it.

@TimothyGu
Copy link
Member

if there's anything you need from the CTC[sic] that's not worth putting on as a separate agenda item

Template needs changing?

@mhdawson
Copy link
Member Author

mhdawson commented Sep 8, 2017

@TimothyGu thanks, I my cut paste/error. @Trott is going to give me some info on how he efficiently created the issues.

@Trott
Copy link
Member

Trott commented Sep 8, 2017

@Trott is going to give me some info on how he efficiently created the issues.

@mhdawson I don't know that it's exactly efficient, but here: https://github.com/nodejs/node/wiki/Creating-a-CTC-Meeting-Issue Lots of room for automation improvements, I suspect.

@fhinkel
Copy link
Member

fhinkel commented Sep 9, 2017

@williamkapke Do you feel like renaming the meeting on the official calendar? Thanks 🙇 !

@williamkapke
Copy link
Contributor

@fhinkel k- I think I got them changed.

On another note: I hope to continue to observe TSC meetings when I can.

@mhdawson
Copy link
Member Author

@williamkapke I'll add you to the list of observers.

@thefourtheye
Copy link
Contributor

Time for TSC chair & Director nominations is over as per #326. I think we should discuss this.

@mhdawson
Copy link
Member Author

@thefourtheye agreed, I was just about to add it to the agenda.

@MylesBorins
Copy link
Contributor

Last minute addition if we have time

[v8.x] deps: backport V8 update to 6.1

@mhdawson
Copy link
Member Author

Minutes for todays meeting #349

@Trott
Copy link
Member

Trott commented Sep 14, 2017

Reminder for @nodejs/tsc and usual observers: The TSC meeting next week will be at September 20 at 12:00 UTC.

That will be noon if you're in Iceland.

It will be 5 AM if you are in California.

It will be 8 AM if you are in Ottawa or New York.

It will be 2 PM if you are in Amsterdam, Berlin, or Rome.

3 PM if you are in Moscow.

5:30 PM in Chennai.

8 PM in China.

9 PM in Tokyo.

10 PM in Sydney.

I've updated the Node.js calendar which should make it easy to get your local time for the meeting wherever you are. It seems to do it automatically. (Pro-tip: If you need to enter UTC times, selecting Iceland as the meeting location is a good thing to do when setting up the meeting in Google Calendar.)

@fhinkel
Copy link
Member

fhinkel commented Oct 11, 2017

I think we can close this.

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

No branches or pull requests

8 participants