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
As the CTC grows and has representation from more time zones, we need to
embrace asynchronous decision making and rely less on the actual
meeting. This change is a proposal for that which, ironically, probably
has to be approved at a meeting.
PR-URL: #8945
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Evan Lucas <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: Julien Gilli <[email protected]>
Reviewed-By: Rod Vagg <[email protected]>
Reviewed-By: Shigeki Ohtsu <[email protected]>
Copy file name to clipboardExpand all lines: GOVERNANCE.md
+21-12Lines changed: 21 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,14 +23,11 @@ The [nodejs/node](https://github.com/nodejs/node) GitHub repository is
23
23
maintained by the CTC and additional Collaborators who are added by the
24
24
CTC on an ongoing basis.
25
25
26
-
Individuals making significant and valuable contributions are made
27
-
Collaborators and given commit-access to the project. These
28
-
individuals are identified by the CTC and their addition as
29
-
Collaborators is discussed during the weekly CTC meeting.
26
+
Individuals identified by the CTC as making significant and valuable
27
+
contributions are made Collaborators and given commit access to the project.
30
28
31
29
_Note:_ If you make a significant contribution and are not considered
32
-
for commit-access, log an issue or contact a CTC member directly and it
33
-
will be brought up in the next CTC meeting.
30
+
for commit access, log an issue or contact a CTC member directly.
34
31
35
32
Modifications of the contents of the nodejs/node repository are made on
36
33
a collaborative basis. Anybody with a GitHub account may propose a
@@ -44,11 +41,9 @@ participate and there is disagreement around a particular
44
41
modification. See [Consensus Seeking Process](#consensus-seeking-process) below
45
42
for further detail on the consensus model used for governance.
46
43
47
-
Collaborators may opt to elevate significant or controversial
48
-
modifications, or modifications that have not found consensus to the
49
-
CTC for discussion by assigning the ***ctc-agenda*** tag to a pull
50
-
request or issue. The CTC should serve as the final arbiter where
51
-
required.
44
+
Collaborators may opt to elevate significant or controversial modifications to
45
+
the CTC by assigning the ***ctc-agenda*** tag to a pull request or issue. The
46
+
CTC should serve as the final arbiter where required.
52
47
53
48
For the current list of Collaborators, see the project
0 commit comments