April 2016 working group meeting

[calvinmetcalf]

tentative plan for first or second week of april

Agenda (to be added to):

• more frequent meetings
• proactively add moar tests (to prevent issues like Piping readable stream to multiple writeable streams results in crash node#5820)
• destroy method rfc: standardize stream.destroy() and pipe node#4401
• flush type thing for writable streams (aka my end pull) stream: add _end method to write streams (equivilent to _flush) node#2314
• reconcile behavior of write(null) between Writable and Trasnform when objectMode: true stream: Writing null to objectMode Transform is unrecoverable node#5711 stream: Support writing null to stream.Transform node#5729
• Remove the use of _events proactively remove use of the _events object #184 events: improve eventEmitter.once() performance node#5127 events: add ability to prepend event listeners node#6032
• error handling
• readable-stream status
• status of whatwg streams
• address issues from Discuss: Gulp looking to move off of Node Streams #181

[mcollina]

Sorry for disappearing. Let's plan this again for next week (4/4) or the week after that (4/10)?

[calvinmetcalf]

doodle link http://doodle.com/poll/5rn4evy4vp54pw63

cc @nodejs/streams @chrisdickinson @domenic @mcollina @mafintosh @ sonewman @rvagg @yoshuawuyts @jmm @stevemao @shinnn @ofrobots @TriAnMan @indutny

[yunong]

I'd like to join this meeting.

[calvinmetcalf]

everyone's invited

[yoshuawuyts]

✨ yay! ✨ Looks like living in Australia isn't ideal, but... all filled in!

I quite like the initial agenda. Perhaps something to add: talk on how to turn streams WG meetings from annually into something a bit more frequent - monthly? bi-monthly?

Oh, perhaps also talk about docs? If we've got time that is, it looks like it's a pretty packed agenda already hah.

Looking forward to talking to you all (if the doodle schedule allows it)! 😁

[mcollina]

Added one more entry.

This look like a long meeting. Should we prioritize a bit into three categories: how we work going forward, stuff we need to handle asap, and breaking changes?

[calvinmetcalf]

ok sounds good, reordered

[sonewman]

I feel pretty out of touch with the currently issues, so if there are any other open issues from from the main nodejs repo it would be good to link them here.

[mcollina]

@sonewman I added some more context. Let me know if this clearer now, or point out what is missing.

[calvinmetcalf]

ok guys I'm tentatively scheduling for Monday the 11th and 1pm est (local time) sorry @yoshuawuyts we will try to make the next one Australian accessible

[mcollina]

@calvinmetcalf are we using hangouts? Should we make that public? Anybody knows how the CTC handles this kind of stuff?

[calvinmetcalf]

we used a hangout last time and that seemed to work, the ctc uses uberconference from what I can tell but I have no experience with that.

[sonewman]

@mcollina awesome, thanks. @calvinmetcalf sounds good, i'll try my best to make it!

[calvinmetcalf]

ok I'll plan on making a hangout and posting a link to it on monday unless anyone has objections

[mcollina]

Go ahead
Il giorno ven 8 apr 2016 alle 18:11 Calvin Metcalf notifications@github.com
ha scritto:

ok I'll plan on making a hangout and posting a link to it on monday unless
anyone has objections

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#183 (comment)

[calvinmetcalf]

ok should be able to join the event via this link at 1.

edit this link https://hangouts.google.com/call/4thltpfez5ft3dgpjcrpivbugme

[calvinmetcalf]

agenda/notes: https://docs.google.com/document/d/1f4GuVR8EfBN3YhPSm1R-x2VOY1WMb7XJ2aBMW86-hk0/edit?usp=sharing

[mscdex]

Any chance #111 could be brought up at this or the next meeting?

[calvinmetcalf]

next meeting definitely sorry about that