@@ -177,6 +177,31 @@ Their responsibilities are:
177
177
The current members can be found in their
178
178
[ README] ( https://github.com/iojs/roadmap#people ) .
179
179
180
+ ### Addon API
181
+
182
+ The Addon API Working Group is responsible for maintaining the NAN project and
183
+ corresponding _ nan_ package in npm. The NAN project makes available an
184
+ abstraction layer for native add-on authors for both Node.js and io.js,
185
+ assisting in the writing of code that is compatible with many actively used
186
+ versions of Node.js, io.js, V8 and libuv.
187
+
188
+ Their responsibilities are:
189
+
190
+ * Maintaining the [ NAN] ( https://github.com/rvagg/nan ) GitHub repository,
191
+ including code, issues and documentation.
192
+ * Maintaining the [ addon-examples] ( https://github.com/rvagg/node-addon-examples )
193
+ GitHub repository, including code, issues and documentation.
194
+ * Maintaining the C++ Addon API within the io.js project, in subordination to
195
+ the io.js TC.
196
+ * Maintaining the Addon documentation within the io.js project, in
197
+ subordination to the io.js TC.
198
+ * Maintaining the _ nan_ package in npm, releasing new versions as appropriate.
199
+ * Messaging about the future of the io.js and NAN interface to give the
200
+ community advance notice of changes.
201
+
202
+ The current members can be found in their
203
+ [ README] ( https://github.com/rvagg/nan#collaborators ) .
204
+
180
205
## Starting a WG
181
206
182
207
A Working Group is established by first defining a charter that can be
0 commit comments