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

Add working group state per Project Lifecycle. #1880

Closed
wants to merge 2 commits into from
Closed

Add working group state per Project Lifecycle. #1880

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e58e804
Add working group state per Project Lifecycle.
mikeal Jun 3, 2015
797761a
Tracing is mature, addons is core.
mikeal Jun 4, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
18 changes: 18 additions & 0 deletions WORKING_GROUPS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,8 @@ back in to the TC.

### [Website](https://github.com/nodejs/website)

**State** : Mature

The website working group's purpose is to build and maintain a public
website for the `io.js` project.

Expand All @@ -43,6 +45,8 @@ releases and features.

### [Streams](https://github.com/nodejs/readable-stream)

**State** : Core

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
Expand All @@ -62,6 +66,8 @@ responsibilities include:

### [Build](https://github.com/nodejs/build)

**State** : Core

The build working group's purpose is to create and maintain a
distributed automation infrastructure.

Expand All @@ -74,6 +80,8 @@ Its responsibilities are:

### [Tracing](https://github.com/nodejs/tracing-wg)

**State** : Mature

The tracing working group's purpose is to increase the
transparency of software written in io.js.

Expand All @@ -86,6 +94,8 @@ Its responsibilities are:

### i18n

**State** : Mature

The i18n working groups handle more than just translations. They
are endpoints for community members to collaborate with each
other in their language of choice.
Expand Down Expand Up @@ -143,6 +153,8 @@ Each language community maintains its own membership.

### [Evangelism](https://github.com/nodejs/evangelism)

**State** : Mature

The evangelism working group promotes the accomplishments
of io.js and lets the community know how they can get involved.

Expand All @@ -157,6 +169,8 @@ content.

### [Roadmap](https://github.com/nodejs/roadmap)

**State** : Mature

The roadmap working group is responsible for user community outreach
and the translation of their concerns into a plan of action for io.js.

Expand All @@ -171,6 +185,8 @@ Their responsibilities are:

### [Docker](https://github.com/nodejs/docker-iojs)

**State** : Mature

The Docker working group's purpose is to build, maintain, and improve official
Docker images for the `io.js` project.

Expand All @@ -182,6 +198,8 @@ Their responsibilities are:

### [Addon API](https://github.com/nodejs/nan)

**State** : Core

The Addon API Working Group is responsible for maintaining the NAN project and
corresponding _nan_ package in npm. The NAN project makes available an
abstraction layer for native add-on authors for both Node.js and io.js,
Expand Down