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