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 2018-05-02 #536

Closed
mhdawson opened this issue Apr 30, 2018 · 8 comments
Closed
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Apr 30, 2018

Time

UTC Wed 02-May-2018 22:00 (10:00 PM):

Timezone Date/Time
US / Pacific Wed 02-May-2018 15:00 (03:00 PM)
US / Mountain Wed 02-May-2018 16:00 (04:00 PM)
US / Central Wed 02-May-2018 17:00 (05:00 PM)
US / Eastern Wed 02-May-2018 18:00 (06:00 PM)
London Wed 02-May-2018 23:00 (11:00 PM)
Amsterdam Thu 03-May-2018 00:00 (12:00 AM)
Moscow Thu 03-May-2018 01:00 (01:00 AM)
Chennai Thu 03-May-2018 03:30 (03:30 AM)
Hangzhou Thu 03-May-2018 06:00 (06:00 AM)
Tokyo Thu 03-May-2018 07:00 (07:00 AM)
Sydney Thu 03-May-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
  • Proposal: add all new core modules under a scope? (too late for http2)
    #389 (wrt. fs/promises)

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

I will not be able to participate because it is too late for me.

@mhdawson
Copy link
Member Author

I'm travelling on Wednesday so I don't think I'll make it. @fhinkel will Chair this week.

@cjihrig
Copy link
Contributor

cjihrig commented May 1, 2018

I'm on vacation, so I won't be able to make it.

@MylesBorins
Copy link
Contributor

MylesBorins commented May 1, 2018 via email

@joyeecheung
Copy link
Member

joyeecheung commented May 2, 2018

I am adding #389 to the agenda to raise awareness of #389 (comment) .

#389 (comment)

I'd like to propose that we hold off on adding any other new core modules until we have reached consensus on this

#389 (comment)

That kind of blanket ban isn't necessary. We have a guidelines in place for this already and there are no proposals for new modules currently planned. On the off chance something does come up, we can hold off landing it until this is settled.

Turns out we did introduce a new module fs/promises without settling down the issue.

Key question: is the module id fs/promises final? Can it be changed after we somehow resolve #389 ? It is experimental, but without a flag. Should we do something about this?

IMO We should have a consistent story around these new modules with potential namespace conflicts - with a new scope introduced or not. If a module being experimental means the module id is subject to change, then we should make the message clear, so whoever tries it would know the risk.

@ChALkeR
Copy link
Member

ChALkeR commented May 2, 2018

As usual, this is too late for me in local time (and I have to get up early on Thursdays), so I will have to miss this. Sorry.

On a side note, I suggest moving meeting times to either of these two:

  • 17 UTC + 21 UTC (rotating between 2):
    { avg: .7510, min: .2587, stdev: .2354, fair: .7250, n5: 14 }
  • 12 UTC + 17 UTC + 21 UTC (rotating between 3):
    { avg: .5967, min: .3165, stdev: .1507, fair: .7792, n5: 13 }

Could be reproduced by copy-pasting the meeting table into https://chalker.github.io/Lliira/.

@Trott
Copy link
Member

Trott commented May 2, 2018

Moderation Team Update: No Moderation Team actions to report this week.

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

@Trott
Copy link
Member

Trott commented May 2, 2018

Minutes in #537

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

7 participants