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.

Sign up for GitHub

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

Jump to bottom

Node.js Foundation Technical Steering Committee (TSC) Meeting 2018-09-26 #605

Closed
mhdawson opened this issue Sep 24, 2018 · 13 comments
Closed

Node.js Foundation Technical Steering Committee (TSC) Meeting 2018-09-26 #605

mhdawson opened this issue Sep 24, 2018 · 13 comments
Assignees
@mhdawson

Comments

@mhdawson
Copy link
Member

mhdawson commented Sep 24, 2018 •
edited
Loading

Time

UTC Wed 26-Sep-2018 21:00 (09:00 PM):

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

  • [WiP] buffer: runtime-deprecate buffer constructor in sync mode #22584

nodejs/admin

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
@mhdawson mhdawson self-assigned this Sep 24, 2018
@MylesBorins
Copy link
Contributor

MylesBorins commented Sep 24, 2018 via email

@Trott
Copy link
Member

Trott commented Sep 24, 2018 •
edited
Loading

I have a conflict and will not be able to attend this week

Rather than leave a comment, you can put 👎 on the original post to indicate you can't make it. (Leaving a comment rather than messaging privately so that others who may not know can get the message too. 👍 means you will make it. 😕 means you don't know if you can make it or not.)

@Trott
Copy link
Member

Trott commented Sep 24, 2018 •
edited
Loading

Regarding "how to do feature detection", it would be great to get resolution on #604. So far, 8 TSC members have definitively weighed in as to whether or not they believe we should ship fs.mkdir() with the recursive option in 10.x. If @nodejs/tsc folks who don't appear in #604 (comment) could let their opinion be known unambiguously (in favor, oppose, abstain), that would be great.

@Trott
Copy link
Member

Trott commented Sep 24, 2018

(By the way, #604 is a call for a vote, so please participate. As I note in the issue, any TSC member can stop the vote by insisting that more conversation should be had to try to reach consensus. While I implore you not to do that, there's nothing I or another TSC member can do to stop you.)

@Trott
Copy link
Member

Trott commented Sep 25, 2018

Removing "how to do feature detection #22585" from the agenda. (I'm the one who put it on.)

@ladyleet
Copy link

Adding nodejs/admin#211 (Node + JS Interactive updates) to the agenda.

@gabrielschulhof
Copy link

I'm not certain I'll be able to make today's meeting. Not quite ready to say 👎 yet, though.

@Trott
Copy link
Member

Trott commented Sep 26, 2018 •
edited
Loading

nodejs/node#22584 was added to the agenda by @seishun. They added it 19 days ago with the comment:

Adding to the agenda because a decision needs to be made soon, otherwise we'll just run out of time.

So... basically, the request is that the TSC decide on whether or not this would be permissible to go into 11.0.

We can't punt on this much more. People who have an opinion should make it clear. People who don't have an opinion (or don't have time to formulate an informed opinion) should also make that clear, so that the others can be responsible for the decision-making here.

We've punted on this for two weeks. Let's not do it a third.

As I see it, the TSC has two options here:

  • Do nothing, in which case this does not go into 11.x because @addaleax objects.
  • Call for a vote to make that determination.

While I'm not opposed to the first option, I don't like the optics. It's basically, "Something got elevated to the TSC and they never did anything with it." So I'm calling for a vote. I expect lots of abstentions. There is nothing wrong with that. Please abstain away! Just don't remain silent. That gums up the works. Make your abstention explicit!

@Trott
Copy link
Member

Trott commented Sep 26, 2018 •
edited
Loading

EDIT: Moving this vote-counting over to nodejs/node#22584 (comment). Go there.

Tallying votes for nodejs/node#22584.

@nodejs/tsc If you are not listed below or you are listed in the wrong place, please edit this comment and update it.

Note that this is not a vote on the pull request itself, but on the general concept/approach landing in 11.0.0 if the implementation comes together and the pull request gets sufficient review/approval in time.

YES, this can land in Node.js 11.0 if the implementation gets ironed out in time--in other words, not necessarily approving that pull request, but approving the concept of the warning going into 11.0 at all:

NO, this should not land in Node.js 11.x:

  • @addaleax
  • @mhdawson (from the discussion in the issue I'm not convinced it makes sense to rush it into 11.x)

ABSTAIN, I do not have an opinion, or do not have time to formulate an informed opinion, and defer to other TSC members on this question:

Note that a "YES" vote here is not a guarantee that you will approve of the ultimate implementation. Your vote may change based on information that comes to light between now and then. But a "NO" result here will certainly stop anyone from rushing to get it done so it can get into 11.0, which is the right thing to do if it has no chance of getting into 11.0

@mcollina
Copy link
Member

Unfortunately the wifi of my hotel stopped working and I cannot join the call.

@mhdawson
Copy link
Member Author

Still waiting for people to join, will start in a few minutes.

@mhdawson
Copy link
Member Author

PR for minutes: #605

@Trott
Copy link
Member

Trott commented Sep 26, 2018

Sorry I'm late on this, but Moderation Team activity in the last week:

Closed a code-of-conduct trolling issue, locked the conversation, and blocked the user. Moderation repo issue 232.

That's it!

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

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

@mhdawson mhdawson

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@mcollina @MylesBorins @Trott @gabrielschulhof @ladyleet @mhdawson