Ohm-Management - Projektarbeit B-ME
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

2015-01-30.md 2.2KB

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