@@ -34,36 +34,32 @@ The current members can be found in their
3434
3535### Streams
3636
37- The streams working group's purpose is to improve the existing Stream
38- implementation, in accordance with the communities needs and feedback.
39-
40- Its responsibilities are:
41- * Produce a living ` Stream ` standard.
42- * Create a reference implementation as ` readable-stream ` .
43- * Recommend versions of ` readable-stream ` to be included in ` io.js `
44- * Collaborate with the WHATWG Stream standard to ensure an optimal level
45- of compatibility between the two standards.
37+ The Streams WG is dedicated to the support and improvement of the Streams API
38+ as used in io.js and the npm ecosystem. We seek to create a composable API that
39+ solves the problem of representing multiple occurrences of an event over time
40+ in a humane, low-overhead fashion. Improvements to the API will be driven by
41+ the needs of the ecosystem; interoperability and backwards compatibility with
42+ other solutions and prior versions are paramount in importance. Our
43+ responsibilities include:
44+
45+ * Addressing stream issues on the io.js issue tracker.
46+ * Authoring and editing stream documentation within the io.js project.
47+ * Reviewing changes to stream subclasses within the io.js project.
48+ * Redirecting changes to streams from the io.js project to this project.
49+ * Assisting in the implementation of stream providers within io.js.
50+ * Recommending versions of readable-stream to be included in io.js.
51+ * Messaging about the future of streams to give the community advance notice of changes.
4652
4753Initial members are:
4854* @chrisdickinson
4955* @isaacs
5056* @rvagg
51- * @TooTallNate
5257* @Raynos
5358* @calvinmetcalf
54- * @substack
5559* @sonewman
5660* @mafintosh
5761* @timgestson
58- * @deoxxa
59- * @maxogden
60- * @feross
61- * @mafintosh
62- * @calvinmetcalf
63- * @sonewman
6462* @domenic
65- * @timgestson
66-
6763
6864### Build
6965
0 commit comments