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 2017-10-25 #396

Closed
mhdawson opened this issue Oct 24, 2017 · 11 comments
Closed
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Oct 24, 2017

Time

UTC Wed 25-Oct-2017 22:00 (10:00 PM):

Timezone Date/Time
US / Pacific Wed 25-Oct-2017 15:00 (03:00 PM)
US / Mountain Wed 25-Oct-2017 16:00 (04:00 PM)
US / Central Wed 25-Oct-2017 17:00 (05:00 PM)
US / Eastern Wed 25-Oct-2017 18:00 (06:00 PM)
Amsterdam Thu 26-Oct-2017 00:00 (12:00 AM)
Moscow Thu 26-Oct-2017 01:00 (01:00 AM)
Chennai Thu 26-Oct-2017 03:30 (03:30 AM)
Hangzhou Thu 26-Oct-2017 06:00 (06:00 AM)
Tokyo Thu 26-Oct-2017 07:00 (07:00 AM)
Sydney Thu 26-Oct-2017 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.

WG update

  • Update from the moderation team (Forrest)

nodejs/node

  • Support both OpenSSL 1.1.0 and 1.0.2 #16130
  • util,assert: expose util.isDeepStrictEqual() #16084
  • buffer: runtime-deprecate Buffer ctor by default #15346
  • stream: move prefixed files into internal/streams. #11957
  • Enable explicit .m.js intent for ESM #16170

nodejs/TSC

  • Proposal to form a Governance Working Group #383
  • Who should be in @nodejs/security? Who should have access to the private repo? #358

nodejs/admin

  • doc: doc expectations on TSC and CommComm members #12

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)
  • Forrest L Norvell @othiym23 (Moderation team member for moderation update)

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 Oct 24, 2017
@mhdawson
Copy link
Member Author

mhdawson commented Oct 24, 2017

Manually added * Enable explicit .m.js intent for ESM #16170

@mhdawson mhdawson changed the title Node.js Foundation Node.js Foundation Technical Steering Committee (TSC) Meeting 2017-10-25 Node.js Foundation Technical Steering Committee (TSC) Meeting 2017-10-25 Oct 24, 2017
@fhinkel
Copy link
Member

fhinkel commented Oct 24, 2017

Sorry, I won't make it to this meeting. Midnight is way too spooky in October 🎃 👻.

@mcollina
Copy link
Member

I won’t make it either

@MylesBorins
Copy link
Contributor

Are we planning to invite any observers for the governance conversation or do we plan to push it off to the working session?

@dshaw
Copy link
Contributor

dshaw commented Oct 25, 2017

I am available to join as an observer today, but recommend that the members of the TSC use the time today to align on how to proceed with #383 and seek consensus on whether a small team can be empowered to work on Governance.

@joyeecheung
Copy link
Member

Probably won't be able to make it...

@addaleax
Copy link
Member

This is pretty late in Europe, if I’m there I’m there, but no promises.

@evanlucas
Copy link
Contributor

I've been pretty sick for the past two days, so I probably won't make it today. I'm still trying to catch up on everything

@othiym23
Copy link

I threw together some quick and dirty slides for the moderation team update, viewable here: https://docs.google.com/presentation/d/1cN712pneaa7L6_wVl9-M2OpK_2Am8EbarYyoJxxyyYA (some of the linked documents may not be viewable – contact me if you'd like access to them).

@Fishrock123
Copy link
Contributor

good turnout today, max 16 or 17 IIRC

node_livestream_viewers-2017-10-25

@mhdawson
Copy link
Member Author

PR for minutes, #398, closing

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