Repository navigation
April 2016 working group meeting #183
Description
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)betweenWritableandTrasnformwhenobjectMode: truestream: Writing null to objectMode Transform is unrecoverable node#5711 stream: Support writing null to stream.Transform node#5729 - Remove the use of
_eventsproactively 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
Activity
mcollina commentedon Mar 29, 2016
Sorry for disappearing. Let's plan this again for next week (4/4) or the week after that (4/10)?
calvinmetcalf commentedon Mar 29, 2016
doodle link http://doodle.com/poll/5rn4evy4vp54pw63
cc @nodejs/streams @chrisdickinson @domenic @mcollina @mafintosh @ sonewman @rvagg @yoshuawuyts @jmm @stevemao @shinnn @ofrobots @TriAnMan @indutny
[-]February 2016 working group meeting [/-][+]April 2016 working group meeting [/+]yunong commentedon Mar 29, 2016
I'd like to join this meeting.
calvinmetcalf commentedon Mar 29, 2016
everyone's invited
yoshuawuyts commentedon Mar 30, 2016
✨ 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 commentedon Mar 31, 2016
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 commentedon Mar 31, 2016
ok sounds good, reordered
sonewman commentedon Apr 3, 2016
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 commentedon Apr 4, 2016
@sonewman I added some more context. Let me know if this clearer now, or point out what is missing.
calvinmetcalf commentedon Apr 4, 2016
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 commentedon Apr 5, 2016
@calvinmetcalf are we using hangouts? Should we make that public? Anybody knows how the CTC handles this kind of stuff?
calvinmetcalf commentedon Apr 5, 2016
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 commentedon Apr 5, 2016
@mcollina awesome, thanks. @calvinmetcalf sounds good, i'll try my best to make it!
calvinmetcalf commentedon Apr 8, 2016
ok I'll plan on making a hangout and posting a link to it on monday unless anyone has objections
mcollina commentedon Apr 8, 2016
Go ahead
Il giorno ven 8 apr 2016 alle 18:11 Calvin Metcalf notifications@github.com
ha scritto:
calvinmetcalf commentedon Apr 11, 2016
ok should be able to join the event via this link at 1.
edit this link https://hangouts.google.com/call/4thltpfez5ft3dgpjcrpivbugme
calvinmetcalf commentedon Apr 11, 2016
agenda/notes: https://docs.google.com/document/d/1f4GuVR8EfBN3YhPSm1R-x2VOY1WMb7XJ2aBMW86-hk0/edit?usp=sharing
mscdex commentedon Apr 11, 2016
Any chance #111 could be brought up at this or the next meeting?
calvinmetcalf commentedon Apr 11, 2016
next meeting definitely sorry about that