Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

io.js Working Groups #599

Closed
wants to merge 3 commits into from
Closed

io.js Working Groups #599

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ecf1b8a
Initial documentation for working groups.
mikeal Jan 24, 2015
f103a3f
Adjusting for feedback in the PR.
mikeal Jan 30, 2015
84539c0
doc: update streams wg charter
chrisdickinson Jan 30, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
doc: update streams wg charter
  • Loading branch information
@chrisdickinson
chrisdickinson committed Jan 30, 2015
commit 84539c056c0378ecdb5cd8462188420153daddbd
34 changes: 15 additions & 19 deletions WORKING_GROUPS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,36 +34,32 @@ The current members can be found in their

### Streams

The streams working group's purpose is to improve the existing Stream
implementation, in accordance with the communities needs and feedback.

Its responsibilities are:
* Produce a living `Stream` standard.
* Create a reference implementation as `readable-stream`.
* Recommend versions of `readable-stream` to be included in `io.js`
* Collaborate with the WHATWG Stream standard to ensure an optimal level
of compatibility between the two standards.
The Streams WG is dedicated to the support and improvement of the Streams API
as used in io.js and the npm ecosystem. We seek to create a composable API that
solves the problem of representing multiple occurrences of an event over time
in a humane, low-overhead fashion. Improvements to the API will be driven by
the needs of the ecosystem; interoperability and backwards compatibility with
other solutions and prior versions are paramount in importance. Our
responsibilities include:

* Addressing stream issues on the io.js issue tracker.
* Authoring and editing stream documentation within the io.js project.
* Reviewing changes to stream subclasses within the io.js project.
* Redirecting changes to streams from the io.js project to this project.
* Assisting in the implementation of stream providers within io.js.
* Recommending versions of readable-stream to be included in io.js.
* Messaging about the future of streams to give the community advance notice of changes.

Initial members are:
* @chrisdickinson
* @isaacs
* @rvagg
* @TooTallNate
* @Raynos
* @calvinmetcalf
* @substack
* @sonewman
* @mafintosh
* @timgestson
* @deoxxa
* @maxogden
* @feross
* @mafintosh
* @calvinmetcalf
* @sonewman
* @domenic
* @timgestson


### Build

Expand Down