Skip to content
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 26 additions & 8 deletions TSC-Charter.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Copy link
Copy Markdown

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.

Copy link
Copy Markdown
Member Author

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.

Copy link
Copy Markdown
Member Author

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.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@gr2m FYI, this section of the charter includes these minimum requirements to stay active:

In the case where an individual TSC member -- within any three month period -- attends fewer than 25% of the regularly scheduled meetings, does not participate in TSC discussions, and does not participate in TSC votes, the member shall be automatically removed from the TSC. The member may be invited to continue attending TSC meetings as an observer.

(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.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The 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.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The 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

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The 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.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about Working Group or Team?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd be good with that.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The 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.
Expand Down Expand Up @@ -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
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The 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.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The 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.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Instead of accusations of Code of Conduct or policy violations, it may be less loaded to describe them as reports of Code of Conduct or policy violations or complaints rather than accusations.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The 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