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-11-29 #429

Closed
mhdawson opened this issue Nov 27, 2017 · 15 comments
Closed
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Nov 27, 2017

Time

UTC Wed 29-Nov-2017 17:00 (05:00 PM):

Timezone Date/Time
US / Pacific Wed 29-Nov-2017 09:00 (09:00 AM)
US / Mountain Wed 29-Nov-2017 10:00 (10:00 AM)
US / Central Wed 29-Nov-2017 11:00 (11:00 AM)
US / Eastern Wed 29-Nov-2017 12:00 (12:00 PM)
Amsterdam Wed 29-Nov-2017 18:00 (06:00 PM)
Moscow Wed 29-Nov-2017 20:00 (08:00 PM)
Chennai Wed 29-Nov-2017 22:30 (10:30 PM)
Hangzhou Thu 30-Nov-2017 01:00 (01:00 AM)
Tokyo Thu 30-Nov-2017 02:00 (02:00 AM)
Sydney Thu 30-Nov-2017 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

  • Enable explicit .m.js intent for ESM #16170
  • buffer: runtime-deprecate Buffer(num) by default #15608
  • timers: setInterval interval includes cb duration #14815

nodejs/TSC

  • Strategic Initiatives - Tracking Issue #423
  • Register Node specific MIME types #371

Other

  • Foundation Medium blog post on modules

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 Nov 27, 2017
@MylesBorins
Copy link
Contributor

I think #16170 can be dropped for now

@jasnell do we have any update on #371?

@fhinkel
Copy link
Member

fhinkel commented Nov 27, 2017

I probably won't make it this week.

@Trott
Copy link
Member

Trott commented Nov 28, 2017

Observers this week should include @danbev and @williamkapke.

I'm going to have a hard time making this one but I'll try.

@MylesBorins
Copy link
Contributor

MylesBorins commented Nov 28, 2017 via email

@mhdawson
Copy link
Member Author

@Trott I'd be happy if you just added the observers to the issue as opposed to in a comment.

@mhdawson
Copy link
Member Author

@jasnell you added #16170, do you agree we should remove ?

@Trott
Copy link
Member

Trott commented Nov 28, 2017

@Trott I'd be happy if you just added the observers to the issue as opposed to in a comment.

I think if I do that, they don't get notified. But I'm happy to do that in addition to commenting! :-D

@Trott
Copy link
Member

Trott commented Nov 28, 2017

(Also: @mhdawson I corrected Michaël Zasso's name here and in the Google doc. It was showing up as MichëZasso, so you've got the umlaut showing up now, but missing a couple characters after it....)

@mhdawson
Copy link
Member Author

@Trott thanks, it comes from here: https://github.com/mhdawson/create-node-meeting-artifacts/blob/master/templates/invited_TSC. I can never tell if missing characters are because of the overwrite that often happens with the special characters or something is missing. I'll see if I can add that single character.

@mhdawson
Copy link
Member Author

@Trott updating an commenting +1

@targos
Copy link
Member

targos commented Nov 28, 2017

BTW I don't mind if you omit the accent in my name, if that can help.

@jasnell
Copy link
Member

jasnell commented Nov 28, 2017

No update on #371

@danbev
Copy link
Contributor

danbev commented Nov 28, 2017

I'm probably going to miss this one I'm afraid

@williamkapke
Copy link
Contributor

Thanks for the invite. I’m onsite at MasterCard this week & I’m on network lockdown. Sry to miss- I’ll catch the YouTube video later.

@mhdawson
Copy link
Member Author

PR for minutes: #430

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