-
-
Notifications
You must be signed in to change notification settings - Fork 140
charter: add TSC membership terms, mandatory mediation, and removal requirements #318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 1 commit
1e51330
928eb4f
7e61300
9e8dc17
86a5ca3
903b9d0
5b6abdc
4085455
e2c48a2
298ad2a
01c868f
4ba8680
6766814
7b6d2ae
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -36,16 +36,25 @@ approved by the Board. | |
|
|
||
| ## Section 4. Establishment of the TSC. | ||
|
|
||
| TSC memberships are not time-limited. There is no maximum size of the TSC. | ||
| The size is expected to vary in order to ensure adequate coverage of important | ||
| areas of expertise, balanced with the ability to make decisions efficiently. | ||
| The TSC must have at least three members. | ||
| TSC memberships are limited to 2 consecutive year periods. An individual | ||
| members term starts at 12am GMT the day after their nomination to the TSC | ||
| is approved and ends precisely two years later. Individuals may be nominated | ||
| to the TSC multiple times but at least one year must pass between terms. | ||
|
|
||
| There is no maximum size of the TSC. The size is expected to vary in order to | ||
| ensure adequate coverage of important areas of expertise, balanced with the | ||
| ability to make decisions efficiently. The TSC must have at least three members. | ||
|
|
||
| Individuals nominated to the TSC must be members of at least one Node.js | ||
| Working Group at the time of their nomination and must maintain active | ||
| participation in at least one Working Group throughout their term. | ||
|
||
|
|
||
| There is no specific set of requirements or qualifications for TSC | ||
| membership beyond these rules. The TSC may add additional members to the | ||
| TSC by a standard TSC motion and vote. A TSC member may be removed from the | ||
| TSC by voluntary resignation, by a standard TSC motion, or in accordance to the | ||
| participation rules described below. | ||
| membership beyond these rules. | ||
|
|
||
| The TSC may add additional members to the TSC by a standard TSC motion and vote. | ||
| A TSC member may be removed from the TSC by voluntary resignation, by a standard | ||
| TSC motion, or in accordance to the participation rules described below. | ||
|
|
||
| Changes to TSC membership should be posted in the agenda, and may be suggested | ||
| as any other agenda item. | ||
|
|
@@ -216,6 +225,15 @@ TSC. | |
| * **Maintainer**: a Collaborator within a Core Project elected to | ||
| represent the Core Project on the TSC. | ||
|
|
||
| ## Section 11. Escalation of Disputes and Code of Conduct Violations | ||
|
|
||
| Participation in the Node.js project is governed by a Code of Conduct policy | ||
| that is established by the TSC. Any accusations of Code of Conduct or policy | ||
|
||
| violations on the part of TSC members will be referred to binding, independent | ||
| third party mediation under the oversight of the Node.js Foundation Board. All | ||
| TSC members, upon acceptance of their nomination to the TSC body, voluntarily | ||
| agree to abide by the decisions of the independent third party mediator. | ||
|
|
||
| [Consensus Seeking]: http://en.wikipedia.org/wiki/Consensus-seeking_decision-making | ||
| [Condorcet]: http://en.wikipedia.org/wiki/Condorcet_method | ||
| [Single Transferable Vote]: http://en.wikipedia.org/wiki/Single_transferable_vote | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest a higher number, at least 5, given the TSC’s responsibility 3 people is to few. I would also suggest to document what happens if the number falls below the minimum.
Another topic that might fit better into a follow up pull request is to require "active" members, and define what "active" means, to avoid a situation where people are voted into the board without fulfilling their responsibilities.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-1 on making the minimum five. What happens if the number falls below this is the responsibility of the Node.js Foundation Board to determine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Regarding "active" members, the TSC recently passed modification to the TSC Charter that includes specific guidelines around TSC member activity. Specifically, there is a minimum participation requirement already covered by the charter.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gr2m FYI, this section of the charter includes these minimum requirements to stay active:
(Not saying there isn't room for improvement. Just pointing out what's already there.)