Node.js Foundation Core Technical Committee (CTC) Meeting 2016-10-26 #9261
Comments
|
One important thing:
Two other things:
|
|
If you have agenda items to add, maybe comment here and/or add them to the doc sooner rather than later. Right now, there is only one item, and it is probably not something that we are likely to have the meeting for. In other words, the meeting right now is (in my estimation) very likely to be canceled unless people have important and/or urgent agenda items to add. (Aside: I think that's a good thing. I think it suggests that decision-making is happening in other venues like GitHub and email. Those venues discriminate by time zone less than meetings do.) |
|
I am unlikely to be able to attend. |
|
Can we please put #8913 on the agenda |
|
+1 to add #8913. I have been using that as the starting point for new contributors here, to help them learn about the contributing process. It would be better if we concluded on what exactly needs to be done. Main problem is that, naming anonymous functions make their names different in the stacktrace and as per #9250 (comment), it looks like the problem is not solved completely. |
|
I won't be able to attend unfortunately. |
|
@nodejs/ctc as both myself and mikeal are unlikely to attend it is prudent that someone get set up to livestream it ahead of time. I wrote a guide on the TSC repo on how to set up OBS for this: https://github.com/nodejs/TSC/blob/master/Streaming/Setting-Up-Open-Brodcaster-Software.md Please let me know if you have any questions and I will try to answer them. Note: you're not going to have a good time trying to stream from macOS. Windows or Linux is much easier/less costly. |
|
I don't think I'll be able to make it this week. I'm at a conference. |
|
I will probably be 10 min late or so. |
|
@Trott FWIW the 'Or in your local time:' links still use the original meeting time. |
|
will there be a recording or a broadcast of this meeting? |
|
@soleboxy There’s a “Public participation” section in the OP here that explains everything. The short answer is https://www.youtube.com/c/nodejs+foundation/live. :) |
|
my schedule is not going to permit me to make it today, my apologies. I will definitely be around next week |
|
@addaleax wrote:
Although given that neither of the two people who usually handle streaming will be attending this week, and no one has spoken up to say that they have taken the time to get the streaming set up together, I'm guessing streaming isn't going to happen this week. We will have minutes, so there's that at least... Given the agenda and the attendees (where some of the people most invested in the two agenda items won't be making it this week), this promises to be a very short meeting. |
|
I forgot about the new schedule, thank you to whoever took notes! |
|
Oops, I forgot about the time change too. Sorry! |
|
Ummm, did anyone stream this? 😬 |
Nope. :-( |
Time
UTC Wed 26-Oct-2016 16: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/TSC
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: