Closed Trott closed 6 years ago
Reminder that I'm on vacation all next week and @mhdawson will be chairing this meeting.
There are six items labeled ctc-review
, although given that there are 5 items on the agenda, including a high-profile controversial subject, I'd recommend focusing on trying to resolve as many of those agenda items as possible in GitHub before the meeting.
ctc-agenda
items can be found at https://github.com/search?utf8=%E2%9C%93&q=label%3Actc-agenda&type=.
ctc-review
items can be found at https://github.com/search?utf8=%E2%9C%93&q=label%3Actc-review&type=.
It might be possible I will not be able to join, as I am traveling in an unfavorable timezone. Regarding the streams issues, I might not be needed if some other ctc members weight in. I'll do my best to join.
The current problem is that there seems no consensus on https://github.com/nodejs/node/issues/445#issuecomment-310028610. The streams WG thinks the best path forward is to add new properties to the classes (b solution), but @mscdex (and maybe others) objects that as it will pollute all descendants. If we want https://github.com/nodejs/node/issues/445 solved, we need to pick a path forward.
I won't be joining, I'll be on the road at the time of the call.
I haven't had time to work on nodejs/node#13784. I suggest taking it off the agenda unless there is anything new to discuss. It was discussed last time but not untagged afterwards.
An emphatic -1 to #165 and, by $deity, let it be the last time this affair comes up.
No strong opinion on the other issues. nodejs/node#445 and nodejs/vm#9 don't seem objectionable to me and I don't quite understand why nodejs/node#12857 is controversial.
I'm still looking for a volunteer to stream.
I'm still looking for a volunteer to stream.
@Fishrock123 Are you likely to be able to make this meeting?
I can volunteer but I'm not sure what are the technical requirements
@targos There are two markdown documents in https://github.com/nodejs/TSC/tree/master/Streaming that hopefully answer the question. Otherwise, Rod and Jeremiah are the two folks who usually do it, so you can ask them if you have questions.
I believe we will also have to discuss https://github.com/nodejs/TSC/pull/317 in some form.
Are you likely to be able to make this meeting?
I should be able to, yes.
There have been no objections raised in regards https://github.com/nodejs/TSC/pull/317. Given that fact, I believe we can simply proceed with landing that PR and assuming that the decision is complete. There's no need to discuss things that are not contentious.
I think for posterity it should at least be mentioned at the start of the meeting. Should we mark this as a TSC meeting and not a CTC meeting? Or both this week?
I have updated the invite list to include @joshgav as a TSC member rather than an observer, and have updated the (CTC)
markers next to everyone's name to read (TSC)
.
We should mark this as a TSC meeting. There's no point in having both.
I worry that may cause some confusion for people not so in-tune what is going on.
@mhdawson let us know if you need anyone from @nodejs/n-api to drop in to discuss nodejs/vm#9. Both myself and @aruneshchandra are available if you need us.
Please read my statement in #165 if you haven't already done so and are planning on submitting a vote in this meeting. If you are voting based on factors separate to those stated in the post or those not covered by my statement then I would appreciate the chance to speak to those factors. I will try and make it, although it's 2am for me so forgive me if I'm not there.
@digitalinfinity can you chime in on https://github.com/nodejs/node/pull/14902 (related to nodejs/vm#9) to fill in how the discussion went on CS modules.
@mhdawson done
Time
UTC Wed 30-Aug-2017 16:00 (04:00 PM):
Or in your local time:
Links
Agenda
Extracted from ctc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
_writableState
and_readableState
access across codebase #445nodejs/vm
nodejs/CTC
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.