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 2018-04-11 #518

Closed
mhdawson opened this issue Apr 9, 2018 · 10 comments
Closed
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Apr 9, 2018

Time

UTC Wed 11-Apr-2018 22:00 (10:00 PM):

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

  • doc: add documentation on porting from Buffer(arg) usage #19827
  • Tracking Issue for Runtime Deprecation of Buffer constructor #19079

nodejs/TSC

  • Tracking issue for updating TSC on Board Meetings #476
  • Strategic Initiatives - Tracking Issue #423

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

Zoom link: https://zoom.us/j/611357642
Regular password

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 Apr 9, 2018
@mcollina
Copy link
Member

The meeting is too late for me and I won't be able to join.

@targos
Copy link
Member

targos commented Apr 11, 2018

Same for me. My apologies.

@MylesBorins
Copy link
Contributor

Unfortunately I have dinner reservations during the meeting today, I will have to miss.

Nothing to add re: buffer stuff. No updates with board. Will post any updates re: modules after today's meeting

@TimothyGu
Copy link
Member

I'll have to miss as well due to conflicts with a class.

@danbev
Copy link
Contributor

danbev commented Apr 11, 2018

Sorry, I'm going to have to skip as well (it will be a late meeting for me and just had too little sleep lately).

@Trott
Copy link
Member

Trott commented Apr 11, 2018

Moderation Team update: A URL was redacted from an issue title. The URL is suspected of being used to distribute malware. Nothing else to report this week. Moderation repo issue 190.

@nodejs/tsc @nodejs/community-committee @nodejs/moderation

@cjihrig
Copy link
Contributor

cjihrig commented Apr 11, 2018

I'll most likely miss today's meeting.

@addaleax
Copy link
Member

Same, I’m not feeling so well today and might go to bed pretty early.

@ChALkeR
Copy link
Member

ChALkeR commented Apr 11, 2018

I won't be able to participate today, too late in local time.

@mhdawson
Copy link
Member Author

PR for minutes: #519

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

No branches or pull requests

10 participants