1
1
# Node.js Project Governance
2
2
3
- ## Core Technical Committee
4
-
5
- The Node.js project is governed by a Core Technical Committee (CTC) which is
6
- responsible for high-level guidance of the project.
7
-
8
- The CTC has final authority over this project including:
9
-
10
- * Technical direction
11
- * Project governance and process (including this policy)
12
- * Contribution policy
13
- * GitHub repository hosting
14
- * Conduct guidelines
15
- * Maintaining the list of additional Collaborators
16
-
17
- For the current list of CTC members, see the project
18
- [ README.md] ( ./README.md#current-project-team-members ) .
3
+ The Node.js project is governed by its Collaborators, including a Core Technical
4
+ Committee (CTC) which is responsible for high-level guidance of the project.
19
5
20
6
## Collaborators
21
7
22
8
The [ nodejs/node] ( https://github.com/nodejs/node ) GitHub repository is
23
- maintained by the CTC and additional Collaborators who are added by the
24
- CTC on an ongoing basis.
9
+ maintained by Collaborators who are added by the CTC on an ongoing basis.
25
10
26
11
Individuals identified by the CTC as making significant and valuable
27
12
contributions are made Collaborators and given commit access to the project. If
@@ -44,18 +29,15 @@ be accepted unless:
44
29
the change. Previously-objecting Collaborators do not necessarily have to
45
30
sign-off on the change, but they should not be opposed to it.
46
31
* The change is escalated to the CTC and the CTC votes to approve the change.
47
- This should be used only after other options (especially discussion among
48
- the disagreeing Collaborators) have been exhausted .
32
+ This should only happen if disagreements between Collaborators cannot be
33
+ resolved through discussion .
49
34
50
35
Collaborators may opt to elevate significant or controversial modifications to
51
36
the CTC by assigning the ` ctc-review ` label to a pull request or issue. The
52
37
CTC should serve as the final arbiter where required.
53
38
54
- For the current list of Collaborators, see the project
55
- [ README.md] ( ./README.md#current-project-team-members ) .
56
-
57
- A guide for Collaborators is maintained in
58
- [ COLLABORATOR_GUIDE.md] ( ./COLLABORATOR_GUIDE.md ) .
39
+ * [ Current list of Collaborators] ( ./README.md#current-project-team-members )
40
+ * [ A guide for Collaborators] ( ./COLLABORATOR_GUIDE.md )
59
41
60
42
### Collaborator Activities
61
43
@@ -71,6 +53,20 @@ The CTC periodically reviews the Collaborator list to identify inactive
71
53
Collaborators. Past Collaborators are typically given _ Emeritus_ status. Emeriti
72
54
may request that the CTC restore them to active status.
73
55
56
+ ## Core Technical Committee
57
+
58
+ The Core Technical Committee (CTC) has final authority over this project
59
+ including:
60
+
61
+ * Technical direction
62
+ * Project governance and process (including this policy)
63
+ * Contribution policy
64
+ * GitHub repository hosting
65
+ * Conduct guidelines
66
+ * Maintaining the list of additional Collaborators
67
+
68
+ * [ Current list of CTC members] ( ./README.md#current-project-team-members )
69
+
74
70
## CTC Membership
75
71
76
72
CTC seats are not time-limited. There is no fixed size of the CTC. The CTC
@@ -82,9 +78,10 @@ membership beyond these rules.
82
78
83
79
The CTC may add additional members to the CTC by a standard CTC motion.
84
80
85
- When a CTC member's participation in [ CTC activities] ( #ctc-activities ) has become
86
- minimal for a sustained period of time, the CTC will request that the member
87
- either indicate an intention to increase participation or voluntarily resign.
81
+ When a CTC member's participation in [ CTC activities] ( #ctc-activities ) has
82
+ become minimal for a sustained period of time, the CTC will request that the
83
+ member either indicate an intention to increase participation or voluntarily
84
+ resign.
88
85
89
86
CTC members may only be removed by voluntary resignation or through a standard
90
87
CTC motion.
0 commit comments