Node.js Foundation Core Technical Committee (CTC) Meeting 2016-11-16 #33
Comments
|
Anyone have anything to add to the agenda? It's just one item right now and it's about the meeting schedule. Seems like something we can resolve in the issue tracker. Other notes:
|
|
So far, no agenda items other than the proposed change to the CTC meeting schedule rotation. Since it pains me to think that we'll have a meeting only to talk about scheduling other meetings, I'd opt for canceling this if:
/cc @nodejs/collaborators (in case someone would add something but they're not seeing this because it's in the CTC repo and not the node repo) |
|
This was added to the agenda by @thealphanerd: His specific comment:
That is time-sensitive, so the meeting is on, it would seem. |
|
I'm not sure that's something that we really need to handle in a meeting. It can probably be negotiated between @indutny and LTS to come to an understanding of urgency and take appropriate action. I'll go and comment in that issue but IMO we should still cancel this meeting unless something else comes up. |
|
sgtm On Tue, Nov 15, 2016, 9:07 PM Rod Vagg notifications@github.com wrote:
|
|
LGTM to me too. |
|
OK, so we don't need a meeting for any of those issues. The only other potentially time-sensitive issue is nodejs/node#9529. It is not tagged @ChALkeR: Is it enough on that one to say, "Hey, @nodejs/ctc, look at nodejs/node#9529 because if you don't have anything to add, it's going to land Real Soon Now." Or is it something that we may need to discuss on the call (perhaps in the private section, depending on whether there are specific concerns and what they are)? |
|
Clarification on my above comment: I think the Buffer issue is absolutely important enough to have a meeting for even if it's the only thing we have to talk about. I don't mean to be pressuring anyone to let us skip the meeting. I just don't want to have everyone show up to a meeting if it's not needed. But, yes, the Buffer thing is important to resolve and it's best if we come to a resolution sooner rather than later. |
|
@Trott Hi! I'm looking at the Buffer issue now, I had a very packed schedule this (and last) week. I am not sure if we should revert the «Buffer without new) deprecation (aka land #9529) short-term, but I have a strong opinion that we should deprecate Given that, I'm not sure if it makes sense to deprecate-undeprecate-deprecate Buffer without new too much. I certainly want to have at least another discussion on this matter before we choose any path of moving forward. I still have one hour to get my arguments ready before the meeting =). |
|
@ChALkeR The meeting this week is at the later time, so you have about 5 hours to go right now! :-D |
|
I am running fever. I might not join today. |
|
@Trott Ah, is it? Argh, I got my schedule wrong =). I will get that ready then. I labeled nodejs/node#9529 issue Citing my comment there:
I hope that specific question would be quick enough to discuss. |
|
Maybe consider discussing nodejs/node#9467, there are diffrent opinions about if nodejs/node#9467 is the correct solution and whether it is solving more issues than it creates. I don't see us converging on a solution. |
|
Are we making a call today or not? |
|
I guess we are? |
|
¯_(ツ)_/¯ |
|
YES, we are. @ChALkeR has been preparing his full briefing on the Buffer situation. |
Time
UTC Wed 16-Nov-2016 20:00:
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/CTC
A new New CTC Meeting Schedule Proposal #29
Documentation WG Status#32
nodejs/node
Revert "buffer: runtime deprecation of calling Buffer without new" #9529
tls: fix leak of WriteWrap+TLSWrap combination#9626
src: don't call into VM from AsyncWrap destructor#9467
Invited
Notes
The agenda comes from issues labelled with
ctc-agendaacross 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.
The text was updated successfully, but these errors were encountered: