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: docs/maintainer-guide/governance.md
+20-1Lines changed: 20 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,6 +43,15 @@ It is important to recognize that committership is a privilege, not a right. Tha
43
43
44
44
A Committer who shows an above-average level of contribution to the project, particularly with respect to its strategic direction and long-term health, may be nominated to become a TSC member, described below.
45
45
46
+
#### Process for Adding Committers
47
+
48
+
1. Add the GitHub user to the "ESLint Team" team
49
+
2. Send welcome email with link to maintainer guide
50
+
3. Add committer email to the ESLint team mailing list
51
+
4. Add committer to the README
52
+
5. Invite to Gitter team chatroom
53
+
6. Tweet congratulations to the new committer from the ESLint Twitter account
54
+
46
55
### Technical Steering Committee (TSC)
47
56
48
57
The ESLint project is jointly governed by a Technical Steering Committee (TSC) which is responsible for high-level guidance of the project.
@@ -64,7 +73,6 @@ Changes to TSC membership should be posted in the agenda, and may be suggested a
64
73
65
74
No more than 1/3 of the TSC members may be affiliated with the same employer. If removal or resignation of a TSC member, or a change of employment by a TSC member, creates a situation where more than 1/3 of the TSC membership shares an employer, then the situation must be immediately remedied by the resignation or removal of one or more TSC members affiliated with the over-represented employer(s).
66
75
67
-
68
76
TSC members have additional responsibilities over and above those of a Committer. These responsibilities ensure the smooth running of the project. TSC members are expected to review code contributions, approve changes to this document, manage the copyrights within the project outputs, and attend regular TSC meetings.
69
77
70
78
TSC members fulfill all requirements of Committers, and also:
@@ -81,6 +89,17 @@ To become a TSC member:
81
89
82
90
A Committer is invited to become a TSC member by existing TSC members. A nomination will result in discussion and then a decision by the TSC.
83
91
92
+
#### Process for Adding TSC Members
93
+
94
+
1. Add the GitHub user to the "ESLint TSC" team
95
+
2. Set the GitHub user to be have the "Owner" role for the ESLint organization
96
+
3. Send welcome email with link to maintainer guide
97
+
4. Add TSC member to the README
98
+
5. Invite to Gitter TSC chatroom
99
+
6. Make TSC member an admin on the ESLint team mailing list
100
+
7. Add TSC member as an admin to ESLint Twitter Account on Tweetdeck
101
+
8. Tweet congratulations to the new TSC member from the ESLint Twitter account
102
+
84
103
#### TSC Meetings
85
104
86
105
The TSC meets every other week in the [TSC Meeting](https://gitter.im/eslint/tsc-meetings) chatroom. The meeting is run by
0 commit comments