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
Copy file name to clipboardExpand all lines: GOVERNANCE.md
+17-7Lines changed: 17 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,7 @@ The Node.js Web Team (`@nodejs/web`) maintains Node.js's web presence and relate
11
11
### 1. Node.js Website Team (`@nodejs/nodejs-website`)
12
12
13
13
**Responsibilities:**
14
+
14
15
- Day-to-day technical development of [nodejs.org](https://nodejs.org)
15
16
- Feature development and enhancement
16
17
- Website component creation
@@ -22,16 +23,18 @@ The Website Team maintains final decision authority on website issues and pull r
22
23
### 2. Node.js Web Infrastructure Team (`@nodejs/web-infra`)
23
24
24
25
**Responsibilities:**
26
+
25
27
- Maintenance of CI/CD pipelines for web projects
26
-
- Management of web infrastructure providers*
28
+
- Management of web infrastructure providers\*
27
29
- Establishment of technical standards and best practices
28
30
- Infrastructure access management
29
31
30
-
*Note: This team manages infrastructure specific to the Website (e.g., Vercel). Other shared infrastructure (e.g., Cloudflare) may be managed by other teams such as the Node.js Build WG.
32
+
\*Note: This team manages infrastructure specific to the Website (e.g., Vercel). Other shared infrastructure (e.g., Cloudflare) may be managed by other teams such as the Node.js Build WG.
31
33
32
34
### 3. Node.js Web Standards Team (`@nodejs/web-standards`)
33
35
34
36
**Responsibilities:**
37
+
35
38
- Advisory role on web standards (e.g., Ecma262)
36
39
- Consultation for Node.js Collaborators, TSC, and Web Team on standards-related matters
37
40
- Guidance on standards compliance
@@ -41,6 +44,7 @@ This team consists of Node.js Collaborators and external experts with significan
41
44
### 4. Node.js UX & Design Team (`@nodejs/ux-and-design`)
42
45
43
46
**Responsibilities:**
47
+
44
48
- Advisory role on UX and design matters
45
49
- Development of design guidelines and best practices
46
50
- Consultation on:
@@ -62,19 +66,22 @@ Members are nominated according to the [Collaborator Guide](https://github.com/n
62
66
### Web Infrastructure Team Membership
63
67
64
68
Members are nominated by:
69
+
65
70
- Node.js Technical Steering Committee (TSC)
66
71
- Node.js Build WG, following their Collaborator Guidelines
67
72
- Existing Node.js Web Team members (recommendation only)
68
73
69
74
### Web Standards Team Membership
70
75
71
76
Members are nominated by:
77
+
72
78
- Node.js Technical Steering Committee (TSC)
73
79
- Existing Node.js Web Team members (recommendation only)
74
80
75
81
### UX & Design Team Membership
76
82
77
83
Members are nominated by:
84
+
78
85
- Node.js Technical Steering Committee (TSC)
79
86
- Existing Node.js Web Team members (recommendation only)
80
87
@@ -87,6 +94,7 @@ The current list of all Web Team members across all subteams is maintained in [M
87
94
### TSC Oversight
88
95
89
96
Any website change that expresses a position about a global event or group of people requires explicit [TSC](https://github.com/nodejs/TSC/blob/main/TSC-Charter.md#section-4-responsibilities-of-the-tsc) approval through one of these methods:
97
+
90
98
- Pinging `@nodejs/tsc` and receiving no objections after seven days
91
99
- Emailing `[email protected]` and receiving at least one approval with no objections after seven days
92
100
@@ -110,10 +118,12 @@ The Web Team follows a [Consensus Seeking](http://en.wikipedia.org/wiki/Consensu
110
118
For pull requests to the governance repository:
111
119
112
120
**Items requiring consensus seeking:**
121
+
113
122
- Governance changes
114
123
- Significant process modifications
115
124
116
125
**Items that may be merged with reasonable review time and no dissent:**
126
+
117
127
- Errata fixes
118
128
- Editorial changes
119
129
- Meeting minutes
@@ -136,24 +146,24 @@ Together, these teams work to deliver the best possible web experience for the N
136
146
137
147
By making a contribution to this project, I certify that:
138
148
139
-
* (a) The contribution was created in whole or in part by me and I
149
+
- (a) The contribution was created in whole or in part by me and I
140
150
have the right to submit it under the open source license
141
151
indicated in the file; or
142
152
143
-
* (b) The contribution is based upon previous work that, to the best
153
+
- (b) The contribution is based upon previous work that, to the best
144
154
of my knowledge, is covered under an appropriate open source
145
155
license and I have the right under that license to submit that
146
156
work with modifications, whether created in whole or in part
147
157
by me, under the same open source license (unless I am
148
158
permitted to submit under a different license), as indicated
149
159
in the file; or
150
160
151
-
* (c) The contribution was provided directly to me by some other
161
+
- (c) The contribution was provided directly to me by some other
152
162
person who certified (a), (b) or (c) and I have not modified
153
163
it.
154
164
155
-
* (d) I understand and agree that this project and the contribution
165
+
- (d) I understand and agree that this project and the contribution
156
166
are public and that a record of the contribution (including all
157
167
personal information I submit with it, including my sign-off) is
158
168
maintained indefinitely and may be redistributed consistent with
159
-
this project or the open source license(s) involved.
169
+
this project or the open source license(s) involved.
0 commit comments