WG meeting October 2016

[mcollina]

Hi @nodejs/streams,

I propose the week between the 24th and the 28th for running our wg meeting.

Agenda:

• Versioning strategy Remove isarray dep. #234
• isArray dep inline isArray #238/ Remove isarray dep. #234
• When are we going to drop support for Node v0.10 and v0.12?
• destroy(err) in node.js v8 as part of the stream standard cc @mafintosh
• Status of WHATWG streams cc @thealphanerd
• support for 'flush" in Writable for node.js v8: stream: add _end method to write streams (equivilent to _flush) node#2314
• vendor readable-stream in core.
• testing effort on _readableState  and _writableState cc @mcollina stream, test: Increase the coverage of _readableState and _writableState properties node#8644
• streams4 aka end method, destroy, and error propagation
• doc size npm package is half doc/stream.md #240

cc @thealphanerd @addaleax @mafintosh @calvinmetcalf @bengl @chrisdickinson @yoshuawuyts

If you are ok with this I will send out a doodle.

[calvinmetcalf]

I can do the 26th and latter

[yoshuawuyts]

yup, works for me

[mafintosh]

same

[MylesBorins]

I'm on the road Oct 14 - Nov 1. I'll try to make it work whenever you pick

[mscdex]

Would it be possible to discuss #111 yet?

[calvinmetcalf]

@mcollina we have a date ?

[mcollina]

Sorry, nodeconf.eu happened.
I'll fire up a doodle now.

[mcollina]

Here is the doodle: http://doodle.com/poll/w2wt6yn4xrprwggz.

My bad if this was late :(.

[mcollina]

@mscdex @yoshuawuyts @thealphanerd @addaleax ^^

[calvinmetcalf]

its ok I just got back from a holiday in russia

On Wed, Oct 26, 2016 at 1:40 PM Matteo Collina notifications@github.com
wrote:

Here is the doodle: http://doodle.com/poll/w2wt6yn4xrprwggz.

My bad if this was late :(.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#235 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABE4nxB9AcFhaEebC_iBMab3zN0ibOTXks5q35CWgaJpZM4KJpH7
.

[mcollina]

I'll call it for Monday 31st at 1pm CEST.

[mafintosh]

@mcollina 👍

[calvinmetcalf]

ok I totally didn't realize those times were cest but I should be able to make it though, I may be a smidge tardy

[mcollina]

@calvinmetcalf do you want to move it to a later time? I picked 17:00 because it was the latest you were free.

[calvinmetcalf]

I thought you picked 13:00 cest? which is 7am edt right?

[mcollina]

17:00 CEST, 12:00 EDT.

I can send you a calendar invite if you prefer.

[mafintosh]

So its 17 CEST now instead?

[mcollina]

oooh, I've selected the right time on the doodle, and completely mistyped here. Today I'm sloppy 😅

[calvinmetcalf]

ok that I can make easily

[addaleax]

17:00 CEST should work for me too :)

(I am a bit confused/curious though… are there any countries in Europe which won’t be back on CET after sunday?)

[mafintosh]

@addaleax good point! @mcollina post a UTC time so we don't mess this up haha

[mcollina]

OK. I'm definitely not up to the task 😂😭😱. I can call 16:00 UTC on Monday 31st, but.... feel free to step in and organize this.

[mafintosh]

@mcollina it isn't your fault timezones are hard :) 16:00 UTC it is. thanks for taking the time to organise a new meeting

[mafintosh]

Turns out @yoshuawuyts and I already have a meeting at the same time. Anyway we can move this forward a couple of hours? Or move it to Tuesday?

[addaleax]

Tuesday should work just as well

[mcollina]

I'm ok moving it one hour (or two), later. What time?

[mafintosh]

Tuesday same time?

[mcollina]

Wednesday same time, 16:00 UTC.

Start a new doodle 😂
Il giorno sab 29 ott 2016 alle 01:13 Mathias Buus notifications@github.com
ha scritto:

Tuesday same time?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#235 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADL4zSIbXV5akvEHEcOuC8zP9A8oU95ks5q4oF_gaJpZM4KJpH7
.

[sonewman]

I can do then... Sorry late arrival.

[calvinmetcalf]

ok sounds good

[mcollina]

Youtube page: https://www.youtube.com/watch?v=GVcZu6zgyMo
To join: https://hangouts.google.com/call/7d3hacmj2vbvrnncspabfacvzue

[mcollina]

Minutes of our meeting:

• we slipped some things marked as semver-major in the latest releases, more for safety. Things are currently reviewed before release. However, we might want to look for an automated process in the future.
• we still support old browsers with 1% or less market share, as well as old Node.js versions (down to v0.8). The team goal is to keep supporting those for the time being, and re-evaluate in the next few months.
• reduce the package size: currently this module is downloaded 40 millions time per month, and if we can speed up the downloads by half a second, we will still save humanity a huge amount of time.
  • vendor dependencies that we use and maintain inline isArray #238 (but maybe is better to use bundleDependencies, as noted afterwards), because we want to keep backward compatibility.
  • remove docs
• @calvinmetcalf will champion flush() for WritableStream
• @mafintosh will write an EPS on destroy().

Vendoring readable-stream in core

This was the major topic of the discussion, as we agreed at Interactive EU, we will submit a proposal to have core depend on readable-stream, and not readable-stream pulling from core.

In order to move things forward, I will write an EPS based on the following:

1. we will maintain the build step, as it currently is
2. import the code from nodejs/node into nodejs/readable-stream, and base the build from that
3. vendor readable-stream into core

If things move forward, I would like to present this at the collaborator summit of NINA.

@nodejs/streams, please make edits if things needs changing.