From dea2f90f3719dc5c091f2681a2113c0399f279b4 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Tue, 7 Aug 2018 16:23:39 -0700 Subject: [PATCH] doc: replace _WG_ with _team_ AFAICT, there is no N-API Working Group. There *is* an N-API team, but AFAIK there is no charter etc. (And if I'm wrong and there is, then https://nodejs.org/en/about/working-groups/ needs an update!) --- doc/guides/adding-new-napi-api.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/doc/guides/adding-new-napi-api.md b/doc/guides/adding-new-napi-api.md index 08133eda2a63bf..aad0e6ba7ab9ca 100644 --- a/doc/guides/adding-new-napi-api.md +++ b/doc/guides/adding-new-napi-api.md @@ -23,9 +23,9 @@ N-API API. * There **should** be at least one test case per interesting use of the API. * There **should** be a sample provided that operates in a realistic way (operating how a real addon would be written). -* A new API **should** be discussed at the N-API working group meeting. +* A new API **should** be discussed at the N-API team meeting. * A new API addition **must** be signed off by at least two members of - the N-API WG. + the N-API team. * A new API addition **should** be simultaneously implemented in at least one other VM implementation of Node.js. * A new API **must** be considered experimental for at least one minor @@ -39,8 +39,7 @@ N-API API. following: * A new PR **must** be opened in `nodejs/node` to remove experimental status. This PR **must** be tagged as **n-api** and **semver-minor**. - * Exiting an API from experimental **must** be signed off by the - working group. + * Exiting an API from experimental **must** be signed off by the team. * If a backport is merited, an API **must** have a down-level implementation. * The API **should** be used by a published real-world module. Use of