Skip to content

Adjust charter to simplify automated removal rules #1097

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.

Sign up for GitHub

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

Merged
Trott merged 3 commits into from
Oct 26, 2021
Merged

Adjust charter to simplify automated removal rules #1097

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ce1a30a
Adjust charter to simplify automated removal rules
Trott Oct 11, 2021
91ae8d4
fixup! Adjust charter to simplify automated removal rules
Trott Oct 11, 2021
07989c9
chore: use remark to format TSC-Charter.md
Trott Oct 12, 2021
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
24 changes: 12 additions & 12 deletions TSC-Charter.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,11 +62,11 @@ through accessible public postings.

TSC members are expected to regularly participate in TSC activities.

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.
A TSC member is automatically removed from the TSC if, during a 3-month period,
all of the following are true:

* They attend fewer than 25% of the regularly scheduled meetings.
* They do not participate in any TSC votes.

## Section 4. Responsibilities of the TSC

Expand All @@ -83,7 +83,7 @@ including:
* Maintaining the list of additional Collaborators.
* Development process and any coding standards.
* Mediating technical conflicts between Collaborators or Foundation
projects.
projects.

The TSC will define Node.js project’s release vehicles.

Expand Down Expand Up @@ -171,14 +171,14 @@ looking to participate in the development effort.
## Section 9. Definitions

* **Contributors**: contribute code or other artifacts, but do not have
the right to commit to the code base. Contributors work with the
project’s Collaborators to have code committed to the code base. A
Contributor may be promoted to a Collaborator by the TSC. Contributors should
rarely be encumbered by the TSC and never by the CPC or OpenJS Foundation Board.
the right to commit to the code base. Contributors work with the
project’s Collaborators to have code committed to the code base. A
Contributor may be promoted to a Collaborator by the TSC. Contributors should
rarely be encumbered by the TSC and never by the CPC or OpenJS Foundation Board.

* **Project**: a technical collaboration effort, e.g. a subsystem, that
is organized through the project creation process and approved by the
TSC.
is organized through the project creation process and approved by the
TSC.

[Condorcet]: https://en.wikipedia.org/wiki/Condorcet_method
[Consensus Seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
Expand Down