11# Node.js Project Governance
22
3- ## Technical Committee
3+ ## Core Technical Committee
44
5- The Node.js project is jointly governed by a Technical Steering Committee (TSC )
5+ The Node.js project is jointly governed by a Core Technical Committee (CTC )
66which is responsible for high-level guidance of the project.
77
8- The TSC has final authority over this project including:
8+ The CTC has final authority over this project including:
99
1010* Technical direction
1111* Project governance and process (including this policy)
@@ -14,28 +14,28 @@ The TSC has final authority over this project including:
1414* Conduct guidelines
1515* Maintaining the list of additional Collaborators
1616
17- Initial membership invitations to the TSC were given to individuals who
17+ Initial membership invitations to the CTC were given to individuals who
1818had been active contributors to Node.js, and who have significant
1919experience with the management of the Node.js project. Membership is
2020expected to evolve over time according to the needs of the project.
2121
22- For the current list of TSC members, see the project
22+ For the current list of CTC members, see the project
2323[ README.md] ( ./README.md#current-project-team-members ) .
2424
2525## Collaborators
2626
2727The [ nodejs/node] ( https://github.com/nodejs/node ) GitHub repository is
28- maintained by the TC and additional Collaborators who are added by the
29- TC on an ongoing basis.
28+ maintained by the CTC and additional Collaborators who are added by the
29+ CTC on an ongoing basis.
3030
3131Individuals making significant and valuable contributions are made
3232Collaborators and given commit-access to the project. These
33- individuals are identified by the TC and their addition as
34- Collaborators is discussed during the weekly TC meeting.
33+ individuals are identified by the CTC and their addition as
34+ Collaborators is discussed during the weekly CTC meeting.
3535
3636_ Note:_ If you make a significant contribution and are not considered
37- for commit-access, log an issue or contact a TC member directly and it
38- will be brought up in the next TC meeting.
37+ for commit-access, log an issue or contact a CTC member directly and it
38+ will be brought up in the next CTC meeting.
3939
4040Modifications of the contents of the nodejs/node repository are made on
4141a collaborative basis. Anybody with a GitHub account may propose a
@@ -51,8 +51,8 @@ on the consensus model used for governance.
5151
5252Collaborators may opt to elevate significant or controversial
5353modifications, or modifications that have not found consensus to the
54- TC for discussion by assigning the *** tc -agenda*** tag to a pull
55- request or issue. The TC should serve as the final arbiter where
54+ CTC for discussion by assigning the *** ctc -agenda*** tag to a pull
55+ request or issue. The CTC should serve as the final arbiter where
5656required.
5757
5858For the current list of Collaborators, see the project
@@ -61,39 +61,39 @@ For the current list of Collaborators, see the project
6161A guide for Collaborators is maintained in
6262[ COLLABORATOR_GUIDE.md] ( ./COLLABORATOR_GUIDE.md ) .
6363
64- ## TC Membership
64+ ## CTC Membership
6565
66- TC seats are not time-limited. There is no fixed size of the TC .
66+ CTC seats are not time-limited. There is no fixed size of the CTC .
6767However, the expected target is between 6 and 12, to ensure adequate
6868coverage of important areas of expertise, balanced with the ability to
6969make decisions efficiently.
7070
71- There is no specific set of requirements or qualifications for TC
71+ There is no specific set of requirements or qualifications for CTC
7272membership beyond these rules.
7373
74- The TC may add additional members to the TC by a standard TC motion.
74+ The CTC may add additional members to the CTC by a standard CTC motion.
7575
76- A TC member may be removed from the TC by voluntary resignation, or by
77- a standard TC motion.
76+ A CTC member may be removed from the CTC by voluntary resignation, or by
77+ a standard CTC motion.
7878
79- Changes to TC membership should be posted in the agenda, and may be
80- suggested as any other agenda item (see "TC Meetings" below).
79+ Changes to CTC membership should be posted in the agenda, and may be
80+ suggested as any other agenda item (see "CTC Meetings" below).
8181
82- No more than 1/3 of the TC members may be affiliated with the same
83- employer. If removal or resignation of a TC member, or a change of
84- employment by a TC member, creates a situation where more than 1/3 of
85- the TC membership shares an employer, then the situation must be
86- immediately remedied by the resignation or removal of one or more TC
82+ No more than 1/3 of the CTC members may be affiliated with the same
83+ employer. If removal or resignation of a CTC member, or a change of
84+ employment by a CTC member, creates a situation where more than 1/3 of
85+ the CTC membership shares an employer, then the situation must be
86+ immediately remedied by the resignation or removal of one or more CTC
8787members affiliated with the over-represented employer(s).
8888
89- ## TC Meetings
89+ ## CTC Meetings
9090
91- The TC meets weekly on a Google Hangout On Air. The meeting is run by
92- a designated moderator approved by the TC . Each meeting should be
91+ The CTC meets weekly on a Google Hangout On Air. The meeting is run by
92+ a designated moderator approved by the CTC . Each meeting should be
9393published to YouTube.
9494
95- Items are added to the TC agenda which are considered contentious or
96- are modifications of governance, contribution policy, TC membership,
95+ Items are added to the CTC agenda which are considered contentious or
96+ are modifications of governance, contribution policy, CTC membership,
9797or release process.
9898
9999The intention of the agenda is not to approve or review all patches.
@@ -102,34 +102,31 @@ group of Collaborators.
102102
103103Any community member or contributor can ask that something be added to
104104the next meeting's agenda by logging a GitHub Issue. Any Collaborator,
105- TC member or the moderator can add the item to the agenda by adding
106- the *** tc -agenda*** tag to the issue.
105+ CTC member or the moderator can add the item to the agenda by adding
106+ the *** ctc -agenda*** tag to the issue.
107107
108- Prior to each TC meeting, the moderator will share the Agenda with
109- members of the TC. TC members can add any items they like to the
110- agenda at the beginning of each meeting. The moderator and the TC
108+ Prior to each CTC meeting, the moderator will share the Agenda with
109+ members of the CTC. CTC members can add any items they like to the
110+ agenda at the beginning of each meeting. The moderator and the CTC
111111cannot veto or remove items.
112112
113- The TC may invite persons or representatives from certain projects to
114- participate in a non-voting capacity. These invitees currently are:
115-
116- * A representative from [ build] ( https://github.com/node-forward/build )
117- chosen by that project.
113+ The CTC may invite persons or representatives from certain projects to
114+ participate in a non-voting capacity.
118115
119116The moderator is responsible for summarizing the discussion of each
120117agenda item and sending it as a pull request after the meeting.
121118
122119## Consensus Seeking Process
123120
124- The TC follows a
121+ The CTC follows a
125122[ Consensus Seeking] ( http://en.wikipedia.org/wiki/Consensus-seeking_decision-making )
126123decision making model.
127124
128125When an agenda item has appeared to reach a consensus, the moderator
129126will ask "Does anyone object?" as a final call for dissent from the
130127consensus.
131128
132- If an agenda item cannot reach a consensus, a TC member can call for
129+ If an agenda item cannot reach a consensus, a CTC member can call for
133130either a closing vote or a vote to table the issue to the next
134- meeting. The call for a vote must be approved by a majority of the TC
131+ meeting. The call for a vote must be approved by a majority of the CTC
135132or else the discussion will continue. Simple majority wins.
0 commit comments