streams WG Meeting 2015-01-30
Links
- Google Hangouts Video: http://www.youtube.com/watch?v=I9nDOSGfwZg
- GitHub Issue: https://github.com/iojs/readable-stream/issues/106
- Original Minutes Google Doc: https://docs.google.com/document/d/17aTgLnjMXIrfjgNaTUnHQO7m3xgzHR2VXBTmi03Qii4/
Agenda
Extracted from https://github.com/iojs/readable-stream/labels/wg-agenda prior to meeting.
- adopt a charter #105
- release and versioning strategy #101
- simpler stream creation #102
- proposal: deprecate implicit flowing of streams #99
Minutes
adopt a charter
- group: +1's all around
What versioning scheme should be adopted?
- group: +1’s 3.0.0
- domenic+group: pulling in patches from other sources where appropriate
- mikeal: version independently, suggesting versions for io.js
- mikeal+domenic: work with TC to notify in advance of changes
simpler stream creation
streamline creation of streams
- sam: streamline creation of streams
- domenic: nice simple solution posted
but, we lose the opportunity to change the model may not be backwards incompatible (double check keys)
action item: domenic will check
remove implicit flowing of streams on(‘data’)
- add isFlowing / isPaused
- mikeal: worrying that we’re documenting polyfill methods – confuses users
- domenic: more reflective API is probably good, with warning labels for users
- new section for mad scientists (reflective stream access)
- calvin: name the “third state”
- mikeal: maybe borrow the name from whatwg?
- domenic: we’re missing the “third state”
- consensus: kind of difficult to name the third state
- mikeal: figure out differences in states / compat
- mathias: always flow on data – eliminates third state
- explore what it breaks
action items:
- ask isaac for ability to list packages by what public io.js APIs they use (esp. Stream)
- ask rod/build for infrastructure
- chris: explore the “flow on data” approach
- add isPaused/isFlowing
- add new docs section
- move isPaused to that section
Source
| 1 | # streams WG Meeting 2015-01-30 |
| 2 | |
| 3 | ## Links |
| 4 | |
| 5 | * **Google Hangouts Video**: http://www.youtube.com/watch?v=I9nDOSGfwZg |
| 6 | * **GitHub Issue**: https://github.com/iojs/readable-stream/issues/106 |
| 7 | * **Original Minutes Google Doc**: https://docs.google.com/document/d/17aTgLnjMXIrfjgNaTUnHQO7m3xgzHR2VXBTmi03Qii4/ |
| 8 | |
| 9 | ## Agenda |
| 10 | |
| 11 | Extracted from https://github.com/iojs/readable-stream/labels/wg-agenda prior to meeting. |
| 12 | |
| 13 | * adopt a charter [#105](https://github.com/iojs/readable-stream/issues/105) |
| 14 | * release and versioning strategy [#101](https://github.com/iojs/readable-stream/issues/101) |
| 15 | * simpler stream creation [#102](https://github.com/iojs/readable-stream/issues/102) |
| 16 | * proposal: deprecate implicit flowing of streams [#99](https://github.com/iojs/readable-stream/issues/99) |
| 17 | |
| 18 | ## Minutes |
| 19 | |
| 20 | ### adopt a charter |
| 21 | |
| 22 | * group: +1's all around |
| 23 | |
| 24 | ### What versioning scheme should be adopted? |
| 25 | * group: +1’s 3.0.0 |
| 26 | * domenic+group: pulling in patches from other sources where appropriate |
| 27 | * mikeal: version independently, suggesting versions for io.js |
| 28 | * mikeal+domenic: work with TC to notify in advance of changes |
| 29 | simpler stream creation |
| 30 | |
| 31 | ### streamline creation of streams |
| 32 | * sam: streamline creation of streams |
| 33 | * domenic: nice simple solution posted |
| 34 | but, we lose the opportunity to change the model |
| 35 | may not be backwards incompatible (double check keys) |
| 36 | |
| 37 | **action item:** domenic will check |
| 38 | |
| 39 | ### remove implicit flowing of streams on(‘data’) |
| 40 | * add isFlowing / isPaused |
| 41 | * mikeal: worrying that we’re documenting polyfill methods – confuses users |
| 42 | * domenic: more reflective API is probably good, with warning labels for users |
| 43 | * new section for mad scientists (reflective stream access) |
| 44 | * calvin: name the “third state” |
| 45 | * mikeal: maybe borrow the name from whatwg? |
| 46 | * domenic: we’re missing the “third state” |
| 47 | * consensus: kind of difficult to name the third state |
| 48 | * mikeal: figure out differences in states / compat |
| 49 | * mathias: always flow on data – eliminates third state |
| 50 | * explore what it breaks |
| 51 | |
| 52 | **action items:** |
| 53 | * ask isaac for ability to list packages by what public io.js APIs they use (esp. Stream) |
| 54 | * ask rod/build for infrastructure |
| 55 | * **chris**: explore the “flow on data” approach |
| 56 | * add isPaused/isFlowing |
| 57 | * add new docs section |
| 58 | * move isPaused to that section |
| 59 | |
| 60 |