镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

Node.js Foundation Technical Steering Committee (TSC) Meeting 2019-01-30 #659

Closed

Description

@mhdawson

Time

UTC Wed 30-Jan-2019 21:00 (09:00 PM):

Timezone Date/Time
US / Pacific Wed 30-Jan-2019 13:00 (01:00 PM)
US / Mountain Wed 30-Jan-2019 14:00 (02:00 PM)
US / Central Wed 30-Jan-2019 15:00 (03:00 PM)
US / Eastern Wed 30-Jan-2019 16:00 (04:00 PM)
London Wed 30-Jan-2019 21:00 (09:00 PM)
Amsterdam Wed 30-Jan-2019 22:00 (10:00 PM)
Moscow Thu 31-Jan-2019 00:00 (12:00 AM)
Chennai Thu 31-Jan-2019 02:30 (02:30 AM)
Hangzhou Thu 31-Jan-2019 05:00 (05:00 AM)
Tokyo Thu 31-Jan-2019 06:00 (06:00 AM)
Sydney Thu 31-Jan-2019 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/TSC

  • 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 Jan 28, 2019
  2. Trott commented on Jan 28, 2019

    @Trott
    Member

    Too early to talk about these?:

    We need to make a decision for the release in April.

    And how about this?:

    I know we usually like to let conversation play out, but in this case, I wonder if it might be better to put a stake in the ground at this time or relatively soon.

  3. Trott commented on Jan 28, 2019

    @Trott
    Member

    For #651, do we have a short-term solution already and we're just trying to figure out the long-term solution? @gabrielschulhof @ofrobots

  4. ofrobots commented on Jan 28, 2019

    @ofrobots
    Contributor

    IMO, #651 shouldn't be on the TSC agenda. A short term solution is available and proposed. Discussion needs to continue on the issue for a longer term solution.

  5. ChALkeR commented on Jan 28, 2019

    @ChALkeR
    Member

    I won't be present, not feeling well.

  6. Trott commented on Jan 28, 2019

    @Trott
    Member

    @mhdawson Since you're the one that put the tsc-agenda label on #651: Are you OK removing it?

  7. mhdawson commented on Jan 28, 2019

    @mhdawson
    MemberAuthor

    I'll remove #651 as I think next steps are agreed for now.

  8. mhdawson commented on Jan 28, 2019

    @mhdawson
    MemberAuthor

    Despite the light agenda I would like to still have the meeting and try to follow up on an issue that I've not received any responses on through the TSC mailing list.

    I'm +1 for adding the 2 that @Trott mentioned as well. In terms of #21351 and #22584 I agree it's not too early and on #25747 I think some discussion might also help.

  9. rvagg commented on Jan 29, 2019

    @rvagg
    Member

    No host? I guess we're skipping this one.

  10. targos commented on Jan 29, 2019

    @targos
    Member

    @rvagg the meeting is tomorrow ;)

  11. rvagg commented on Jan 29, 2019

    @rvagg
    Member

    Heh, ok then!

  12. Trott commented on Jan 30, 2019

    @Trott
    Member

    Turns out I probably can't make the meeting today, but if someone else is prepared to frame the Buffer constructor on unhandled rejection conversations, great.

  13. thefourtheye commented on Jan 31, 2019

    @thefourtheye
    Contributor

    There were no significant moderation actions taken in the last week.

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

  14. Trott commented on Jan 31, 2019

    @Trott
    Member

    Minutes PR: #661

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