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 2019-03-27 #676

Closed
mhdawson opened this issue Mar 25, 2019 · 13 comments
Closed

Node.js Foundation Technical Steering Committee (TSC) Meeting 2019-03-27 #676

mhdawson opened this issue Mar 25, 2019 · 13 comments
Assignees
@mhdawson

Comments

@mhdawson
Copy link
Member

Time

UTC Wed 27-Mar-2019 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Wed 27-Mar-2019 09:00 (09:00 AM)
US / Mountain Wed 27-Mar-2019 10:00 (10:00 AM)
US / Central Wed 27-Mar-2019 11:00 (11:00 AM)
US / Eastern Wed 27-Mar-2019 12:00 (12:00 PM)
London Wed 27-Mar-2019 16:00 (04:00 PM)
Amsterdam Wed 27-Mar-2019 17:00 (05:00 PM)
Moscow Wed 27-Mar-2019 19:00 (07:00 PM)
Chennai Wed 27-Mar-2019 21:30 (09:30 PM)
Hangzhou Thu 28-Mar-2019 00:00 (12:00 AM)
Tokyo Thu 28-Mar-2019 01:00 (01:00 AM)
Sydney Thu 28-Mar-2019 03:00 (03: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/Release

  • Preparation for Node.js 12 #417

nodejs/summit

  • Call for Sessions: Berlin Collab Summit #149

nodejs/TSC

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

nodejs/admin

  • Checklist to address changes due to move to OpenJS Foundation #311

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
@mhdawson mhdawson self-assigned this Mar 25, 2019
@Trott
Copy link
Member

Trott commented Mar 25, 2019

nodejs/Release#417 and openjs-foundation/summit#149 were added for visibility/awareness only so they can be covered quickly as part of the Announcements section.

nodejs/admin#311 probably requires some more detailed conversation. Although if that conversation could happen in the issue tracker, that would be preferable IMO. And while that stuff is important and should not be ignored, it is likely not yet urgent?

In short, there may be grounds for canceling the meeting. (Personally, I'd hold off and only cancel if there's an uptick in action on nodejs/admin#311, which could be taken as an indication that the conversation is moving forward without the need for a meeting.)

@rvagg
Copy link
Member

rvagg commented Mar 26, 2019

Re Node 12, more attention and careful thought for supported platforms would be good, still. nodejs/node#26714 (not ready for merge but nearing it)

  • We're settling on GCC-6 where GCC is in use.
  • Almost no feedback on macOS defaults, proposal is to lift minimum supported compile OS to 10.13 and Xcode 10 with minimum supported run OS to 10.11.
  • Python 2/3 is awkward, we're probably going to have to recommend having both out of the gate but with 2 EOL at the end of the year we have to be careful to not lock ourselves into terrible recommendations.

@mhdawson
Copy link
Member Author

I'm out on vacation this week. @mcollina, @danbev, @Trott any chance one of you can chair?

@mhdawson
Copy link
Member Author

mhdawson commented Mar 26, 2019 •
edited
Loading

In respect to nodejs/admin#311, one of the important issues to weigh in on is: nodejs/admin#316. If the meeting is held we should discuss nodejs/admin#316 to see if there is a consensus of the TSC as to what we would prefer.

@Trott
Copy link
Member

Trott commented Mar 26, 2019

I'm out on vacation this week. @mcollina, @danbev, @Trott any chance one of you can chair?

Did you mean to perhaps include @fhinkel?

I can probably chair, although (a) happy if someone else does it (especially because I'm a "probably" and not a "definitely"), and (b) I don't have the elevated privileges or password or whatever is needed for Zoom....

@Trott
Copy link
Member

Trott commented Mar 26, 2019

one of the important issues to weigh in on is: nodejs/admin#316. If the meeting is held we should discuss nodejs/admin#316 to see if there is a consensus of the TSC as to what we would prefer.

So far, there are four TSC members all agreeing to the current process/proposal and no one objecting. I'd definitely encourage people to weigh in on that issue rather than hashing it out at the meeting.

@danbev
Copy link
Contributor

danbev commented Mar 26, 2019

@mhdawson I would have been happy to but this is a meeting time that I can't make.

@Trott
Copy link
Member

Trott commented Mar 26, 2019

On nodejs/admin#316, we're up to 8 TSC members endorsing Myles's status quo proposal and 1 TSC member suggesting a variation (but not appearing to have a problem with status quo). If we do decide to discuss it at the meeting still, the discussion may be a short one.

@Trott
Copy link
Member

Trott commented Mar 26, 2019

Hey, @nodejs/tsc! With @BethGriggs having announced the @nodejs/release semver-major cutoff date for Node.js 12, it's a good idea to go through the list off open PRs labeled semver-major and see if there's anything in there you might want to push along so it can get into 12.x!

https://github.com/nodejs/node/search?q=is%3Apr+is%3Aopen+label%3Asemver-major&type=Issues

OMG, there are 32 pull requests that are open and labeled semver-major. Let's get reviewing! (Probably a good idea to close ones that are unlikely to ever land.)

@cjihrig
Copy link
Contributor

cjihrig commented Mar 26, 2019

Am I the only one that is a little uneasy seeing a few semver major PRs to the module system (especially in light of issues like nodejs/node#26926)?

@MylesBorins
Copy link
Contributor

I'd like to see nodejs/node#26745 added to the agenda for a heads up at the very least. Planning to land tomorrow if there are no objections.

I may not be able to attend the meeting due to TC39 but could likely step out for a specific agenda item if y'all ping me when you need me

@Trott
Copy link
Member

Trott commented Mar 27, 2019

Minutes PR: #679

@Trott Trott closed this as completed Mar 27, 2019
@thefourtheye
Copy link
Contributor

No significant moderation team activity last week.

cc @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
7 participants
@danbev @rvagg @MylesBorins @thefourtheye @Trott @cjihrig @mhdawson