11# Node.js Project Governance
22
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.
195
206## Collaborators
217
228The [ 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.
2510
2611Individuals identified by the CTC as making significant and valuable
2712contributions are made Collaborators and given commit access to the project. If
@@ -44,18 +29,15 @@ be accepted unless:
4429 the change. Previously-objecting Collaborators do not necessarily have to
4530 sign-off on the change, but they should not be opposed to it.
4631* 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 .
4934
5035Collaborators may opt to elevate significant or controversial modifications to
5136the CTC by assigning the ` ctc-review ` label to a pull request or issue. The
5237CTC should serve as the final arbiter where required.
5338
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 )
5941
6042### Collaborator Activities
6143
@@ -71,6 +53,20 @@ The CTC periodically reviews the Collaborator list to identify inactive
7153Collaborators. Past Collaborators are typically given _ Emeritus_ status. Emeriti
7254may request that the CTC restore them to active status.
7355
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+
7470## CTC Membership
7571
7672CTC seats are not time-limited. There is no fixed size of the CTC. The CTC
@@ -82,9 +78,10 @@ membership beyond these rules.
8278
8379The CTC may add additional members to the CTC by a standard CTC motion.
8480
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.
8885
8986CTC members may only be removed by voluntary resignation or through a standard
9087CTC motion.
0 commit comments