From 9d6356324ff782e0837c6efc1a2a2e216ff89a00 Mon Sep 17 00:00:00 2001 From: Antoine du Hamel Date: Wed, 22 Mar 2023 18:56:50 +0100 Subject: [PATCH 1/3] Update charter to concentrate powers to the TSC rather than its voting members The only effect of this change should be that TSC regular members participate in lazy consensus process. If you see another effect that I overlooked, that's not on purpose, so please chime in. The aim of this change is to clarify that TSC voting members do not have any specific powers (except the ones defined by the Moderation Policy and the ones delegated by the TSC on a case by case basis) over Collaborators. --- TSC-Charter.md | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index cd9776a4..34ad204e 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -58,7 +58,7 @@ they do not participate in three consecutive TSC votes. ## Section 4. Responsibilities of the TSC -Subject to such policies as may be set by the CPC, the TSC voting members are +Subject to such policies as may be set by the CPC, the TSC is responsible for all technical development within the Node.js project, including: @@ -73,11 +73,11 @@ including: * Mediating technical conflicts between Collaborators or Foundation projects. -The TSC voting members will define Node.js project’s release vehicles. +The TSC will define Node.js project’s release vehicles. ## Section 5. Node.js Project Operations -The TSC voting members will establish and maintain a development process for the +The TSC will establish and maintain a development process for the Node.js project. The development process will establish guidelines for how the developers and community will operate. It will, for example, establish appropriate timelines for TSC review (e.g. agenda items must be @@ -117,11 +117,11 @@ of terms a TSC Chairperson or voting CPC member may serve. ## Section 7. Voting For internal project decisions, Collaborators shall operate under Lazy -Consensus. The TSC voting members shall establish appropriate guidelines for +Consensus. The TSC shall establish appropriate guidelines for implementing Lazy Consensus (e.g. expected notification and review time periods) within the development process. -The TSC voting members follow a [Consensus Seeking][] decision making model. +The TSC follows a [Consensus Seeking][] decision making model. When an agenda item has appeared to reach a consensus the moderator will ask "Does anyone object?" as a final call for dissent from the consensus. @@ -134,8 +134,7 @@ All changes to this charter must be approved by the CPC. ## Section 8. Project Roles The Node.js git repository is maintained by the TSC and -additional Collaborators who are added by the TSC voting members on an ongoing -basis. +additional Collaborators who are added by the TSC on an ongoing basis. Individuals making significant and valuable contributions are made Collaborators and given commit-access to the project. These individuals are identified by the @@ -146,7 +145,7 @@ basis as defined in the development process. Collaborators may opt to elevate significant or controversial modifications, or modifications that have not found consensus to the TSC for discussion by assigning the `tsc-agenda` tag to a pull request or -issue. The TSC voting members should serve as the final arbiter where required. +issue. TSC votes should serve as the final arbiter where required. The TSC will maintain and publish a list of current Collaborators, as well as a development process guide for Collaborators and Contributors looking to participate in the development effort. From 6994114e8cff481fe11ad5622f2d44882a56fd06 Mon Sep 17 00:00:00 2001 From: Antoine du Hamel Date: Sun, 26 Mar 2023 00:20:04 +0100 Subject: [PATCH 2/3] Update TSC-Charter.md --- TSC-Charter.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index 34ad204e..4be16c92 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -145,7 +145,8 @@ basis as defined in the development process. Collaborators may opt to elevate significant or controversial modifications, or modifications that have not found consensus to the TSC for discussion by assigning the `tsc-agenda` tag to a pull request or -issue. TSC votes should serve as the final arbiter where required. +issue. When consensus cannot be reached, the TSC voting members should serve as the +final arbiter by casting a vote. The TSC will maintain and publish a list of current Collaborators, as well as a development process guide for Collaborators and Contributors looking to participate in the development effort. From 5de79cd70a97b3b9aebe8d333e83749565103133 Mon Sep 17 00:00:00 2001 From: Antoine du Hamel Date: Sun, 26 Mar 2023 00:22:18 +0100 Subject: [PATCH 3/3] line wrapping --- TSC-Charter.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index 4be16c92..fe7eea99 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -145,11 +145,10 @@ basis as defined in the development process. Collaborators may opt to elevate significant or controversial modifications, or modifications that have not found consensus to the TSC for discussion by assigning the `tsc-agenda` tag to a pull request or -issue. When consensus cannot be reached, the TSC voting members should serve as the -final arbiter by casting a vote. -The TSC will maintain and publish a list of current Collaborators, as -well as a development process guide for Collaborators and Contributors -looking to participate in the development effort. +issue. When consensus cannot be reached, the TSC voting members should serve as +the final arbiter by casting a vote. The TSC will maintain and publish a list of +current Collaborators, as well as a development process guide for Collaborators +and Contributors looking to participate in the development effort. ## Section 9. Definitions