nodejs / CTC

Node.js Core Technical Committee & Collaborators
80 stars 27 forks source link

Node.js Foundation Core Technical Committee (CTC) Meeting 2017-06-21 #143

Closed Trott closed 7 years ago

Trott commented 7 years ago

Time

UTC Wed 21-Jun-2017 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Wed 21-Jun-2017 09:00 (09:00 AM)
US / Mountain Wed 21-Jun-2017 10:00 (10:00 AM)
US / Central Wed 21-Jun-2017 11:00 (11:00 AM)
US / Eastern Wed 21-Jun-2017 12:00 (12:00 PM)
Amsterdam Wed 21-Jun-2017 18:00 (06:00 PM)
Moscow Wed 21-Jun-2017 19:00 (07:00 PM)
Chennai Wed 21-Jun-2017 21:30 (09:30 PM)
Hangzhou Thu 22-Jun-2017 00:00 (12:00 AM)
Tokyo Thu 22-Jun-2017 01:00 (01:00 AM)
Sydney Thu 22-Jun-2017 02:00 (02:00 AM)

Or in your local time:

Links

Agenda

Extracted from ctc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

Invited

Observers

Notes

The agenda comes from issues labelled with ctc-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

Uberconference; participants should have the link & numbers, contact me if you don't.

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 CTC that's not worth putting on as a separate agenda item, this is a good place for it.

Trott commented 7 years ago

@nodejs/ctc No issues on the agenda this week. Cancel? Or does someone have something to add?

Trott commented 7 years ago

Here are the current issues and pull requests labeled ctc-review. @nodejs/ctc, please take a look.

Trott commented 7 years ago

This was added to the agenda about two hours ago by @gibfahn:

@gibfahn: Can you indicate either here or in that issue what you hope the CTC will do? (Any chance you meant to add this to the @nodejs/build WG agenda instead of CTC? I could be wrong--paging @williamkapke to make sure I'm not--but I think for the CTC to actually be able to make determinations in how the the build infrastructure is maintained, we'd have to first revoke the Build WG charter, and I don't think we're remotely likely to do that.)

Trott commented 7 years ago

....and just like that, the item is off the agenda. (It was apparently added by accident.)

We're back to zero agenda items. Unless there's something for the private segment, I imagine we're canceling. Anyone feel differently?

rvagg commented 7 years ago

I would like some discussion somewhere about V8 5.9 & perf, maybe a meeting isn't the best forum though?

Trott commented 7 years ago

I would like some discussion somewhere about V8 5.9 & perf, maybe a meeting isn't the best forum though?

Is the idea to determine what the benchmarks need to show before we're willing to do a release with V8 5.9? If so, maybe one of the working groups or proposed working groups would be the place for the conversation? It seems like Release, LTS, and Benchmarking would all be likely to have opinions.

rvagg commented 7 years ago

Is the idea to determine what the benchmarks need to show before we're willing to do a release with V8 5.9

Mainly I'd just like some intentionality about the decision rather than just rolling forward because it feels inevitable.

I'll open a new thread on this repo to figure out next steps rather than continuing to pollute this one.

I guess we don't have anything to cover tomorrow.

ChALkeR commented 7 years ago

I wanted to briefly mention something in the private section. But I can move that to email, if needed.

jasnell commented 7 years ago

If there are no agenda items, then I'm +1 on canceling again this week. Things seem to be running fairly smooth these days, I like it!

Quick update: I believe that we're about two to three weeks out from the initial HTTP/2 PR. I have some work still to do on getting it working properly on Windows and I need to add the runtime/configure flags that allow it to be switched on/off, but the initial basic functionality is largely ready for initial review. Again, the plan is to get it in initially as experimental in 8.x.

cjihrig commented 7 years ago

Also +1 to canceling and taking the private item(s) to email. It's really nice to see things being handled on GitHub.

Trott commented 7 years ago

Closing this issue. Might propose moving meetings to every other week if this keeps up. :-D