Skip to content

Node.js Foundation Technical Steering Committee (TSC) Meeting 2019-06-05 #714

Closed

Description

@mhdawson

Time

UTC Wed 05-Jun-2019 21:00 (09:00 PM):

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

  • src: use cgroups to get memory limits #27508
  • benchmark: refactor buffer benchmarks #26418

nodejs/TSC

  • Reevaluate meeting times #707
  • doc: update TSC charter #698
  • Tracking issue for updating TSC on Board Meetings #476
  • Strategic Initiatives - Tracking Issue #423

Invited

Observers/Guests

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.


Invitees

Please use the following emoji reactions in this post to indicate your
availability.

  • 👍 - Attending
  • 👎 - Not attending
  • 😕 - Not sure yet

Activity

  1. self-assigned this
    on Jun 3, 2019
  2. ChALkeR commented on Jun 3, 2019

    @ChALkeR
    Member

    What about #707 and moving to 15/16/19 UTC timeslots?
    /cc @nodejs/tsc @Trott.

  3. mhdawson commented on Jun 4, 2019

    @mhdawson
    MemberAuthor

    The issue was not generated correctly by the tool, but minutes doc was. Added issues to agenda.

  4. mhdawson commented on Jun 4, 2019

    @mhdawson
    MemberAuthor

    @ChALkeR #707 is on the list.

  5. addaleax commented on Jun 5, 2019

    @addaleax
    Member

    Not sure if I’ll make it, this might actually be a bit late for today (yay for the new schedule!). I think I’ve weighed in on everything on the agenda. If anybody cares for a strategic initiative update for Workers and I don’t happen to be at the meeting (although there’s probably a few people who were in the session and are also being on the call):

    We had a session discussing the state of Workers at the collab summit. We discussed a number of items, and decided that it makes sense to go forward with moving Workers out of experimental state after going through the WebMessaging web platform tests and making sure that our implementation aligns with them (that is currently in progress), and adding Workers-using modules (e.g. workerpool at ~250k downloads/month) to CITGM.

  6. Trott commented on Jun 5, 2019

    @Trott
    Member

    Minutes PR in #715

  7. Trott commented on Jun 5, 2019

    @Trott
    Member

    @nodejs/moderation Any updates?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions