You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit debd6c9
Browse filesBrowse the repository at this point in the historyBrowse files
* Maintaining localization tooling and workflows for the Node.js website.
41
+
* Project governance and process for the Working Group, including its own
42
+
governance, contribution, and permissions policies.
43
+
* Managing the membership of `@nodejs/web` and its subteams, per
44
+
[WG Membership](#wg-membership).
45
+
* Overseeing repositories within the Working Group's scope (archiving, removing)
46
+
and their maintainer teams.
47
+
48
+
The following remain outside the charter:
49
+
50
+
* Website changes expressing a position about a global event or group of people,
51
+
which continue to require TSC approval, per [TSC Oversight](#tsc-oversight)
52
+
below.
53
+
* Website content governed by the [content vs. code][] guidance, including
54
+
OpenJS Foundation requests, per
55
+
[OpenJS Oversight and Content Input](#openjs-oversight-and-content-input)
56
+
below.
57
+
* Cloudflare, which is owned by the [Build WG][]; the Web Working Group holds
58
+
scoped access only. Changing that boundary requires agreement from the
59
+
Build WG.
60
+
61
+
Work that this charter does not place with the WG remains with the TSC or other
62
+
WGs. Within the charter, the TSC's only recourse over a Working Group is to
63
+
revoke its charter. Chartering does not change the two oversight clauses below.
33
64
34
65
### TSC Oversight
35
66
@@ -42,6 +73,8 @@ or by sending an email to `tsc@iojs.org` and receive at least one approval and n
42
73
43
74
Website content including, but not limited to, the [blog](https://nodejs.org/en/blog), [about](https://nodejs.org/en/about), and [partner](https://nodejs.org/en/about/partners) pages are governed by the [content vs. code][] guidance. Additionally, OpenJS Foundation requests are always honored, such as including project and foundation links in the footer.
44
75
76
+
## Teams
77
+
45
78
### Node.js Website Team (`@nodejs/nodejs-website`)
46
79
47
80
The Node.js Website Team is responsible for the day-to-day technical development of the Node.js Website. This is primarily the development of the website itself, adding new features, pages and components, but also fixing any security issues in the website code, handling operational maintenance, and so on.
@@ -62,7 +95,7 @@ Web Infra Team members should have access to maintain the services mentioned abo
62
95
63
96
Members of this team are nominated by current members of the Node.js Web Infra Team or by the Web Working Group, and follow the guidelines provided in the Collaborator Guidelines of the Node.js Build WG. Nominations are decided by the Working Group, as described in [WG Membership](#wg-membership).
64
97
65
-
\* This team has access to infrastructure providers directly related to the Website only, such as Vercel. Other providers that are shared beyond the Website may be controlled by other teams (for example, the Node.js Build WG owns Cloudflare). See the [Charter][] for that boundary.
98
+
\* This team has access to infrastructure providers directly related to the Website only, such as Vercel. Other providers that are shared beyond the Website may be controlled by other teams (for example, the Node.js Build WG owns Cloudflare). See the [Charter][]above for that boundary.
66
99
67
100
When considering new members, approvers are primarily concerned with **competence** and **trust**. The [language within the Build WG pertaining to competence and trust][build-membership] applies here. The following is repeated, for emphasis:
68
101
@@ -299,7 +332,7 @@ The [Node.js Moderation Policy][] applies to this WG.
299
332
The [Node.js Code of Conduct][] applies to this WG.
0 commit comments