Node: Node.js Foundation Core Technical Committee (CTC) Meeting 2016-06-01

[rvagg]

Time

UTC Wed 01-Jun-2016 20:00:

• San Francisco: Wed 01-Jun-2016 13:00
• New York: Wed 01-Jun-2016 16:00
• Amsterdam: Wed 01-Jun-2016 22:00
• Moscow: Wed 01-Jun-2016 23:00
• Sydney: Thu 02-Jun-2016 06:00
• Tokyo: Thu 02-Jun-2016 05:00

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Core%20Technical%20Committee%20(CTC)+Meeting+2016-06-01&iso=20160601T20
• or http://www.wolframalpha.com/input/?i=8pm+UTC%2C+Jun+01%2C+2016+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1rrD5dYjyn2yeTnfAkSvQqtl0fvm1t5vFbxpTtjN1OTI
• _Previous Minutes Google Doc: https://docs.google.com/document/d/1SSLxV3rzXDSN8QFkxIiYt3TktrCvHmdqhpvjl8Z1ky4_
  

  Agenda

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

nodejs/node

• Tracking issue: stdio problems #6980

• doc: add Google Analytics tracking. #6601

  Invited

• Bradley Meck @bmeck (observer/GoDaddy)

• Ben Noordhuis @bnoordhuis (CTC)
• Сковорода Никита Андреевич @ChALkeR (CTC)
• Chris Dickinson @chrisdickinson (CTC)
• Colin Ihrig @cjihrig (CTC)
• Evan Lucas @evanlucas (CTC)
• Jeremiah Senkpiel @Fishrock123 (CTC)
• Fedor Indutny @indutny (CTC)
• James M Snell @jasnell (CTC)
• Josh Gavant @joshgav (observer/Microsoft)
• Michael Dawson @mhdawson (CTC)
• Julien Gilli @misterdjules (CTC)
• Mikeal Rogers @mikeal (observer/Node.js Foundation)
• Brian White @mscdex (CTC)
• Ali Ijaz Sheikh @ofrobots (CTC)
• Alexis Campailla @orangemocha (CTC)
• Bert Belder @piscisaureus (CTC)
• Rod Vagg @rvagg (CTC)
• Seth Thompson @s3ththompson (observer/Google)
• Shigeki Ohtsu @shigeki (CTC)
• Steven R Loomis @srl295 (observer/IBM/ICU)
• Trevor Norris @trevnorris (CTC)
• Rich Trott @Trott (CTC)
  

  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.

[rvagg]

And I'm going to opt out of this one, I need to claw a morning back for myself. I'd love for someone new to put their hand up to facilitate this meeting, it should be a straightforward one to jump and get some practice. If not, I'm sure @jasnell or @Fishrock123 could step up.

My input:

• Tracking issue: stdio problems #6980: I'm +1 on the temporary "fix" for OSX in #6895 given that the user experience is so much different to v5 and prior. I'm also +1 on flushing stderr and stdout on process exit, I _think_ that should be semver-major but am not going to argue that point very hard, I just want to see previous user experience restored (yeah, prior to 1.0.2). Beyond that, the whole question of blocking or non-blocking stdio on tty, or pipes, or whatever, I'm finding this whole area to be very difficult to grok enough to make decisions. What would be nice is an understanding of what other platforms do with stdio, is there a consistent pattern we can conform to in order to align better with what users already have to interact with.
• doc: add Google Analytics tracking. #6601: I've made my thoughts known in there, I'm +1 on this given that it's only for our hosted docs but I sympathise with those who are objecting so I'm not going to make a fuss. I'm not a consumer of the data so don't have much of a stake in this to argue. I'd like to know hear voices of potential consumers of this data make a clear case for it—who is that? the Website WG? Docs WG? The executive?

[rvagg]

Additional thought: @Fishrock123 is the primary person pushing on the stdio stuff, I'm not sure if that's because others don't see any urgency here, whether it's assumed that someone else is taking care of it or whether it's simply too complex to engage with. Just be aware that he could probably do with some assistance forming a clear strategy and getting workable solutions implemented, if you have bandwidth then I'm sure it would be appreciated.

[eljefedelrodeodeljefe]

@rvagg would like to consume the GA data for screenflow analysis of the api docs etc. That is at least known to be easy to implement with it - but doesn't exclude any other solution.

[jasnell]

I can facilitate the call if no one else volunteers :-)

[indutny]

I won't be able to make it today, sorry!

[Trott]

The Standup section of the doc is now ready to go, for people who like to get a jump on that.

I can facilitate if James finds his microphone being non-cooperative with Uberconference or something like that.

[cdnadmin]

Are you guys still posting previous audio at https://soundcloud.com/node-foundation/tracks ? Last one I see is from Feb of this year.

We have the meeting minutes, but like to listen to audio sometimes too (while driving, etc) :-)

Thx, y'all!

[mikeal]

Everything is on youtube. We need to find an automated way to rip the audio out of youtube and publish it to soundcloud.

On Jun 1, 2016, at 12:46PM, Monico Moreno [email protected] wrote:

Are you guys still posting previous audio at https://soundcloud.com/node-foundation/tracks https://soundcloud.com/node-foundation/tracks ? Last one I see is from Feb of this year.

We have the meeting minutes, but like to listen to audio sometimes too (while driving, etc) :-)

Thx, y'all!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/nodejs/node/issues/7091#issuecomment-223103278, or mute the thread https://github.com/notifications/unsubscribe/AAACQ5f5gx7kQnZW4lIyJOM1czUHB8Rnks5qHeGDgaJpZM4IrelZ.

[MylesBorins]

youtube-dl + ffmpeg could do this really easily

edit: I think I could put together some sort of automated process for this if there is an interest

[chrisdickinson]

Sending my apologies.

FWIW, re: GA in Node docs, I'm +1 on including it. More information about how folks are using the docs can help inform how we edit the docs down the line — for instance, if a lot of folks are jumping from one section to another via a particular link, it would be handy to know that in case an edit would destroy that link. IIUC, GA would let us track inter-doc links as well (from anchor to anchor within a single page), which server logs cannot do. Maintaining our own analytics platform is out of scope for solving this problem.

[cdnadmin]

Heads up public participants: YouTube link is actually: https://www.youtube.com/c/nodejs+foundation/live

Working on getting the /c/ in the "Public Part" section above, for future meetings (as referenced in #6968) :-)

Also, per Rod's comment:

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.

[Trott]

I've updated the YouTube link in Rod's original post above.

[MylesBorins]

does not appear to be anything at the /live/ link... taking me to the main list of videos

edit: this is the link we want https://www.youtube.com/c/nodejs+foundation/live

notice the lack a trailing slash... sigh

[Trott]

@TheAlphaNerd Use https://www.youtube.com/c/nodejs+foundation/live. I suspect the trailing slash in the link posted by @cdnadmin is what's giving you a problem.

[cdnadmin]

Correct @Trott Sorry about that @TheAlphaNerd

Comment fixed for others!

[Fishrock123]

Livestream viewers, max 13. Most comment interaction we have had so far.