-
-
Notifications
You must be signed in to change notification settings - Fork 142
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 2 commits
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 for one year terms that must be recertified by a simple | ||
| majority of TSC members every year. Recertified members will continue through | ||
| the next years term. Members failing recertification may return to the TSC | ||
| after no less than six months following normal TSC motion. | ||
|
|
||
| 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. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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.) |
||
|
|
||
| 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. | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This one concerns me a bit. For some areas we have teams as opposed to WGs (ex crypto) and I hate to lose those voices from the TSC. We should look at how many of the current TSC members would be affected by this requirement as I think it would b quite a high number.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The goal here is to strongly encourage TSC members to be more active across the project. Those individuals could easily jump into contributing to Working Groups also
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I guess this also means that people who only contribute to core are excluded. Maybe it could say that they must participate in the Node.js org throughout their term.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. How about
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd be good with that.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd be ok if it was Working Group or Team. |
||
|
|
||
| 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 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This seems like it could be subject to abuse if "any" accusation leads to third party mediation. Perhaps `Code of Conduct violations that involve TSC members that cannot be solved via consensus will be referred to binding, independent third party mediation under the oversight of the Node.js Foundation Board.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We end up in the same boat with the same hand wringing, delays and interpersonal issues. Going immediately to mediation is better. It doesn't have to be involved. This essentially just means that the Foundation picks someone to look at the issue and decide.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nit: Instead of
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I've updated the language here. |
||
| 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.
Nit:
years->year'sQuestion: What does "failing recertification" mean? Does that mean they forget to put in a motion to get recertified? Or does that mean the TSC opted not to renew their term? Whatever the answer, can we clarify the wording to that effect?
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.
What do you recommend here?
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.
@Trott, I've updated the language. Please let me know if I've Whacked-The-Mole adequately.
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.
Yes, thanks.