Skip to content

Commit

Permalink
doc: Add Addon API (NAN) to working group list
Browse files Browse the repository at this point in the history
Also update nan and examples repositories links to io.js organization

PR-URL: #1523
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
  • Loading branch information
julianduque committed Apr 25, 2015
1 parent f3cc50f commit 5178f93
Showing 1 changed file with 5 additions and 4 deletions.
9 changes: 5 additions & 4 deletions WORKING_GROUPS.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,7 @@ back in to the TC.
* [Evangelism](#evangelism)
* [Roadmap](#roadmap)
* [Docker](#docker)
* [Addon API](#addon-api)
* [Starting a Working Group](#starting-a-wg)
* [Bootstrap Governance](#bootstrap-governance)

Expand Down Expand Up @@ -179,7 +180,7 @@ Their responsibilities are:
* Maintain and improve the images' documentation.


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

The Addon API Working Group is responsible for maintaining the NAN project and
corresponding _nan_ package in npm. The NAN project makes available an
Expand All @@ -189,9 +190,9 @@ versions of Node.js, io.js, V8 and libuv.

Their responsibilities are:

* Maintaining the [NAN](https://github.com/rvagg/nan) GitHub repository,
* Maintaining the [NAN](https://github.com/iojs/nan) GitHub repository,
including code, issues and documentation.
* Maintaining the [addon-examples](https://github.com/rvagg/node-addon-examples)
* Maintaining the [addon-examples](https://github.com/iojs/node-addon-examples)
GitHub repository, including code, issues and documentation.
* Maintaining the C++ Addon API within the io.js project, in subordination to
the io.js TC.
Expand All @@ -202,7 +203,7 @@ Their responsibilities are:
community advance notice of changes.

The current members can be found in their
[README](https://github.com/rvagg/nan#collaborators).
[README](https://github.com/iojs/nan#collaborators).

## Starting a WG

Expand Down

0 comments on commit 5178f93

Please sign in to comment.