From 99a287fd75ca831211f3bdb7acc70b805a025885 Mon Sep 17 00:00:00 2001 From: Rod Vagg Date: Sat, 21 Mar 2015 16:16:16 +1100 Subject: [PATCH] doc: add Addon API WG --- WORKING_GROUPS.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/WORKING_GROUPS.md b/WORKING_GROUPS.md index 0e69d7e1a8730b..1f7cbb130beb8f 100644 --- a/WORKING_GROUPS.md +++ b/WORKING_GROUPS.md @@ -177,6 +177,31 @@ Their responsibilities are: The current members can be found in their [README](https://github.com/iojs/roadmap#people). +### Addon API + +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, +assisting in the writing of code that is compatible with many actively used +versions of Node.js, io.js, V8 and libuv. + +Their responsibilities are: + +* Maintaining the [NAN](https://github.com/rvagg/nan) GitHub repository, + including code, issues and documentation. +* Maintaining the [addon-examples](https://github.com/rvagg/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. +* Maintaining the Addon documentation within the io.js project, in + subordination to the io.js TC. +* Maintaining the _nan_ package in npm, releasing new versions as appropriate. +* Messaging about the future of the io.js and NAN interface to give the + community advance notice of changes. + +The current members can be found in their +[README](https://github.com/rvagg/nan#collaborators). + ## Starting a WG A Working Group is established by first defining a charter that can be