From dafb1469ff3dc6142d674bf9f166100cde522331 Mon Sep 17 00:00:00 2001 From: Darshan Sen Date: Fri, 27 Jun 2025 15:07:27 +0530 Subject: [PATCH 01/20] Update charter with communication responsibilities It has been brought up in https://github.com/nodejs/admin/issues/977#issuecomment-3001258778. Signed-off-by: Darshan Sen Co-authored-by: Joyee Cheung --- TSC-Charter.md | 1 + 1 file changed, 1 insertion(+) diff --git a/TSC-Charter.md b/TSC-Charter.md index e049e2d8..aab49fee 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -74,6 +74,7 @@ including: * Development process and any coding standards. * Mediating technical conflicts between Collaborators or Foundation projects. +* Technical communication. The TSC will define Node.js project’s release vehicles. From 04b59af1ecb6bdca8eaac7e0e7b5e5e64b614034 Mon Sep 17 00:00:00 2001 From: Darshan Sen Date: Fri, 27 Jun 2025 17:37:01 +0530 Subject: [PATCH 02/20] Update TSC-Charter.md --- TSC-Charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index aab49fee..30b6d41e 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -74,7 +74,7 @@ including: * Development process and any coding standards. * Mediating technical conflicts between Collaborators or Foundation projects. -* Technical communication. +* Overseeing official communications related to technical content from project contributors. The TSC will define Node.js project’s release vehicles. From 45fe5375739f14c614e3639fd2403406c4f7d975 Mon Sep 17 00:00:00 2001 From: Darshan Sen Date: Fri, 27 Jun 2025 17:52:11 +0530 Subject: [PATCH 03/20] Update TSC-Charter.md Co-authored-by: Joyee Cheung --- TSC-Charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index 30b6d41e..cbba1ab7 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -74,7 +74,7 @@ including: * Development process and any coding standards. * Mediating technical conflicts between Collaborators or Foundation projects. -* Overseeing official communications related to technical content from project contributors. +* Communication about the above that would be considered official, and the development process of said communication. The TSC will define Node.js project’s release vehicles. From 3eecd4fc31fbf84f130804059d316688752eee74 Mon Sep 17 00:00:00 2001 From: Darshan Sen Date: Fri, 27 Jun 2025 20:04:10 +0530 Subject: [PATCH 04/20] Update TSC-Charter.md Co-authored-by: Joyee Cheung --- TSC-Charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index cbba1ab7..d8857228 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -74,7 +74,7 @@ including: * Development process and any coding standards. * Mediating technical conflicts between Collaborators or Foundation projects. -* Communication about the above that would be considered official, and the development process of said communication. +* Official communication about the above and what they govern, and the development process of said communication. The TSC will define Node.js project’s release vehicles. From b74e8104441618fdff3f64f8272124d09a92b512 Mon Sep 17 00:00:00 2001 From: Darshan Sen Date: Sat, 28 Jun 2025 11:45:35 +0530 Subject: [PATCH 05/20] Update TSC-Charter.md Co-authored-by: James M Snell --- TSC-Charter.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index d8857228..f7319991 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -76,7 +76,15 @@ including: projects. * Official communication about the above and what they govern, and the development process of said communication. -The TSC will define Node.js project’s release vehicles. + The TSC will define Node.js project’s release vehicles. + +Specific exclusions from the communication oversight responsibilities include: brand marketing, fundraising and financial sponsorship (including, but not limited to, the OpenJS Foundation's financial sponsorship of the project), legal matters, and marketing/ community events, except when specifically approved by the OpenJS Foundation. + +All uses of OpenJS Foundation-owned trademarks and IP are, of course, subject to review and approval by the Foundation in all project-relevant communication across all media formats and modes in accordance to the OpenJS Foundation Trademark Policy. This includes use of the marks, in full or in part, in domain names, social media account handles, event names and other similar identifiers. + +The TSC may establish project-specific communication channels, such as social media accounts and discussion forums, administered under the oversight of the TSC, subject to the above requirements. Such communication channels must be capable of being administered jointly by both the TSC and the Foundation. + +Nothing in this charter should be interpreted as preventing the Foundation from also publishing about any aspect of the project, including all technical aspects, so long as those communications are not presented as being endorsed by, or representative of, the TSC or the body of project contributors except when specifically approved by the TSC. ## Section 5. Node.js Project Operations From 2107db1757f626f98da57be99ba0ecf8bfa76fcc Mon Sep 17 00:00:00 2001 From: Darshan Sen Date: Sat, 28 Jun 2025 11:46:40 +0530 Subject: [PATCH 06/20] Update TSC-Charter.md --- TSC-Charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index f7319991..563e3a22 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -76,7 +76,7 @@ including: projects. * Official communication about the above and what they govern, and the development process of said communication. - The TSC will define Node.js project’s release vehicles. +The TSC will define Node.js project’s release vehicles. Specific exclusions from the communication oversight responsibilities include: brand marketing, fundraising and financial sponsorship (including, but not limited to, the OpenJS Foundation's financial sponsorship of the project), legal matters, and marketing/ community events, except when specifically approved by the OpenJS Foundation. From a198eee5442c1a475cfa8652c3c988212933f547 Mon Sep 17 00:00:00 2001 From: Darshan Sen Date: Sat, 28 Jun 2025 11:47:49 +0530 Subject: [PATCH 07/20] Update TSC-Charter.md --- TSC-Charter.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index 563e3a22..8b1ffcd9 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -78,7 +78,14 @@ including: The TSC will define Node.js project’s release vehicles. -Specific exclusions from the communication oversight responsibilities include: brand marketing, fundraising and financial sponsorship (including, but not limited to, the OpenJS Foundation's financial sponsorship of the project), legal matters, and marketing/ community events, except when specifically approved by the OpenJS Foundation. +Specific exclusions from the communication oversight responsibilities include: + +* Brand marketing +* Fundraising and financial sponsorship (including, but not limited to, the OpenJS Foundation's financial sponsorship of the project) +* Legal matters +* Marketing/ community events + +except when specifically approved by the OpenJS Foundation. All uses of OpenJS Foundation-owned trademarks and IP are, of course, subject to review and approval by the Foundation in all project-relevant communication across all media formats and modes in accordance to the OpenJS Foundation Trademark Policy. This includes use of the marks, in full or in part, in domain names, social media account handles, event names and other similar identifiers. From 934c4373cbee395273d745a028627f904080c422 Mon Sep 17 00:00:00 2001 From: Darshan Sen Date: Sat, 28 Jun 2025 11:49:29 +0530 Subject: [PATCH 08/20] Update TSC-Charter.md Signed-off-by: Darshan Sen --- TSC-Charter.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index 8b1ffcd9..7cdd5462 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -85,13 +85,13 @@ Specific exclusions from the communication oversight responsibilities include: * Legal matters * Marketing/ community events -except when specifically approved by the OpenJS Foundation. +except when specifically approved by the OpenJS Foundation. -All uses of OpenJS Foundation-owned trademarks and IP are, of course, subject to review and approval by the Foundation in all project-relevant communication across all media formats and modes in accordance to the OpenJS Foundation Trademark Policy. This includes use of the marks, in full or in part, in domain names, social media account handles, event names and other similar identifiers. +All uses of OpenJS Foundation-owned trademarks and IP are, of course, subject to review and approval by the Foundation in all project-relevant communication across all media formats and modes in accordance to the OpenJS Foundation Trademark Policy. This includes use of the marks, in full or in part, in domain names, social media account handles, event names and other similar identifiers. -The TSC may establish project-specific communication channels, such as social media accounts and discussion forums, administered under the oversight of the TSC, subject to the above requirements. Such communication channels must be capable of being administered jointly by both the TSC and the Foundation. +The TSC may establish project-specific communication channels, such as social media accounts and discussion forums, administered under the oversight of the TSC, subject to the above requirements. Such communication channels must be capable of being administered jointly by both the TSC and the Foundation. -Nothing in this charter should be interpreted as preventing the Foundation from also publishing about any aspect of the project, including all technical aspects, so long as those communications are not presented as being endorsed by, or representative of, the TSC or the body of project contributors except when specifically approved by the TSC. +Nothing in this charter should be interpreted as preventing the Foundation from also publishing about any aspect of the project, including all technical aspects, so long as those communications are not presented as being endorsed by, or representative of, the TSC or the body of project contributors except when specifically approved by the TSC. ## Section 5. Node.js Project Operations From d0b783c8e8c563c7586a8b63bceb6618facc3127 Mon Sep 17 00:00:00 2001 From: Darshan Sen Date: Tue, 1 Jul 2025 12:34:36 +0530 Subject: [PATCH 09/20] Update TSC-Charter.md Co-authored-by: Joyee Cheung --- TSC-Charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index 7cdd5462..ddf75bb2 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -89,7 +89,7 @@ except when specifically approved by the OpenJS Foundation. All uses of OpenJS Foundation-owned trademarks and IP are, of course, subject to review and approval by the Foundation in all project-relevant communication across all media formats and modes in accordance to the OpenJS Foundation Trademark Policy. This includes use of the marks, in full or in part, in domain names, social media account handles, event names and other similar identifiers. -The TSC may establish project-specific communication channels, such as social media accounts and discussion forums, administered under the oversight of the TSC, subject to the above requirements. Such communication channels must be capable of being administered jointly by both the TSC and the Foundation. +The community may establish project-specific communication channels, such as social media accounts and discussion forums, subject to the above requirements. If the communication channels are used to represent the project, administrator access should be granted to both the TSC and the Foundation for oversight, while the day-to-day operation can be delegated to another party as long as they respect the consensus seeking process of the project. Nothing in this charter should be interpreted as preventing the Foundation from also publishing about any aspect of the project, including all technical aspects, so long as those communications are not presented as being endorsed by, or representative of, the TSC or the body of project contributors except when specifically approved by the TSC. From eee844d77fed2eec7a15a7f7eeddac1b57c351d3 Mon Sep 17 00:00:00 2001 From: Darshan Sen Date: Tue, 1 Jul 2025 19:44:41 +0530 Subject: [PATCH 10/20] Update TSC-Charter.md --- TSC-Charter.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/TSC-Charter.md b/TSC-Charter.md index ddf75bb2..a8042fab 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -78,6 +78,15 @@ including: The TSC will define Node.js project’s release vehicles. +The communication oversight responsibilities include: + +* Technical development processes of the project +* Releases and release announcements +* Technical documentation +* Contributor onboarding and conduct +* Project governance +* Technical direction + Specific exclusions from the communication oversight responsibilities include: * Brand marketing From 30fd0794d3656848dd098dbcc758718d9ae68c0f Mon Sep 17 00:00:00 2001 From: Darshan Sen Date: Tue, 1 Jul 2025 21:07:24 +0530 Subject: [PATCH 11/20] Update TSC-Charter.md --- TSC-Charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index a8042fab..6c2b3410 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -74,7 +74,7 @@ including: * Development process and any coding standards. * Mediating technical conflicts between Collaborators or Foundation projects. -* Official communication about the above and what they govern, and the development process of said communication. +* Establishing and stewarding a consensus-seeking process to represent the technical community and its work in external communications. The TSC will define Node.js project’s release vehicles. From 5eb3c7c434b2615f36d5a6116e0f8a651ffb9055 Mon Sep 17 00:00:00 2001 From: Darshan Sen Date: Wed, 2 Jul 2025 11:33:27 +0530 Subject: [PATCH 12/20] Update TSC-Charter.md Co-authored-by: Joyee Cheung --- TSC-Charter.md | 1 - 1 file changed, 1 deletion(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index 6c2b3410..8281416e 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -96,7 +96,6 @@ Specific exclusions from the communication oversight responsibilities include: except when specifically approved by the OpenJS Foundation. -All uses of OpenJS Foundation-owned trademarks and IP are, of course, subject to review and approval by the Foundation in all project-relevant communication across all media formats and modes in accordance to the OpenJS Foundation Trademark Policy. This includes use of the marks, in full or in part, in domain names, social media account handles, event names and other similar identifiers. The community may establish project-specific communication channels, such as social media accounts and discussion forums, subject to the above requirements. If the communication channels are used to represent the project, administrator access should be granted to both the TSC and the Foundation for oversight, while the day-to-day operation can be delegated to another party as long as they respect the consensus seeking process of the project. From 3a75b169e3e8b3a89d668b73186238c42f02ea05 Mon Sep 17 00:00:00 2001 From: Darshan Sen Date: Wed, 2 Jul 2025 11:34:56 +0530 Subject: [PATCH 13/20] Update TSC-Charter.md --- TSC-Charter.md | 1 - 1 file changed, 1 deletion(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index 8281416e..638b57a3 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -96,7 +96,6 @@ Specific exclusions from the communication oversight responsibilities include: except when specifically approved by the OpenJS Foundation. - The community may establish project-specific communication channels, such as social media accounts and discussion forums, subject to the above requirements. If the communication channels are used to represent the project, administrator access should be granted to both the TSC and the Foundation for oversight, while the day-to-day operation can be delegated to another party as long as they respect the consensus seeking process of the project. Nothing in this charter should be interpreted as preventing the Foundation from also publishing about any aspect of the project, including all technical aspects, so long as those communications are not presented as being endorsed by, or representative of, the TSC or the body of project contributors except when specifically approved by the TSC. From ad6cace2e76aab8414a55502808889885cffd49a Mon Sep 17 00:00:00 2001 From: Darshan Sen Date: Wed, 2 Jul 2025 16:47:21 +0530 Subject: [PATCH 14/20] Update TSC-Charter.md --- TSC-Charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index 638b57a3..91492014 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -94,7 +94,7 @@ Specific exclusions from the communication oversight responsibilities include: * Legal matters * Marketing/ community events -except when specifically approved by the OpenJS Foundation. +Communication on excluded oversight areas that intersect with included responsibilities will be handled in collaboration with the OpenJS Foundation. The community may establish project-specific communication channels, such as social media accounts and discussion forums, subject to the above requirements. If the communication channels are used to represent the project, administrator access should be granted to both the TSC and the Foundation for oversight, while the day-to-day operation can be delegated to another party as long as they respect the consensus seeking process of the project. From d6c528c45a570bc8a4a0c76f40fffba1386328ad Mon Sep 17 00:00:00 2001 From: Darshan Sen Date: Wed, 2 Jul 2025 16:47:40 +0530 Subject: [PATCH 15/20] Update TSC-Charter.md --- TSC-Charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index 91492014..c14bd7d6 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -98,7 +98,7 @@ Communication on excluded oversight areas that intersect with included responsib The community may establish project-specific communication channels, such as social media accounts and discussion forums, subject to the above requirements. If the communication channels are used to represent the project, administrator access should be granted to both the TSC and the Foundation for oversight, while the day-to-day operation can be delegated to another party as long as they respect the consensus seeking process of the project. -Nothing in this charter should be interpreted as preventing the Foundation from also publishing about any aspect of the project, including all technical aspects, so long as those communications are not presented as being endorsed by, or representative of, the TSC or the body of project contributors except when specifically approved by the TSC. +If the TSC becomes aware of external communications that appear inconsistent with the project’s consensus, it may engage with the communicating party, directly or through appropriate channels, to help align the message with the project’s consensus-seeking processes. ## Section 5. Node.js Project Operations From 29dc94962f12d60fe79c59934bd9851880c40382 Mon Sep 17 00:00:00 2001 From: Darshan Sen Date: Wed, 2 Jul 2025 20:52:47 +0530 Subject: [PATCH 16/20] Update TSC-Charter.md Co-authored-by: Joyee Cheung --- TSC-Charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index c14bd7d6..e2833dba 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -96,7 +96,7 @@ Specific exclusions from the communication oversight responsibilities include: Communication on excluded oversight areas that intersect with included responsibilities will be handled in collaboration with the OpenJS Foundation. -The community may establish project-specific communication channels, such as social media accounts and discussion forums, subject to the above requirements. If the communication channels are used to represent the project, administrator access should be granted to both the TSC and the Foundation for oversight, while the day-to-day operation can be delegated to another party as long as they respect the consensus seeking process of the project. +If a Node.js-specific communication channel, such as a social media account or a discussion forum, is established by another party and used to represent the technical work or the technical community of the project, the TSC may request administrator or moderator access to ensure representation is aligned with the consensus within the project. Day-to-day operation in such channels can be delegated to another party as long as they follow the Code of Conduct, and respect the consensus seeking process before representation of the project is manifested. If the TSC becomes aware of external communications that appear inconsistent with the project’s consensus, it may engage with the communicating party, directly or through appropriate channels, to help align the message with the project’s consensus-seeking processes. From a59433ef252f142a897830af924be4dce485f47c Mon Sep 17 00:00:00 2001 From: Darshan Sen Date: Thu, 3 Jul 2025 09:19:18 +0530 Subject: [PATCH 17/20] Update TSC-Charter.md Co-authored-by: Joyee Cheung --- TSC-Charter.md | 18 +----------------- 1 file changed, 1 insertion(+), 17 deletions(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index e2833dba..760a07c2 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -78,23 +78,7 @@ including: The TSC will define Node.js project’s release vehicles. -The communication oversight responsibilities include: - -* Technical development processes of the project -* Releases and release announcements -* Technical documentation -* Contributor onboarding and conduct -* Project governance -* Technical direction - -Specific exclusions from the communication oversight responsibilities include: - -* Brand marketing -* Fundraising and financial sponsorship (including, but not limited to, the OpenJS Foundation's financial sponsorship of the project) -* Legal matters -* Marketing/ community events - -Communication on excluded oversight areas that intersect with included responsibilities will be handled in collaboration with the OpenJS Foundation. +Communication on topics where the scope of the TSC intersects with that of the [OpenJS CPC](https://github.com/openjs-foundation/cross-project-council/blob/main/CPC-CHARTER.md) or the [OpenJS board](https://images.prismic.io/openjsf/c31b195a-83c9-4d89-9d92-d0cb8840ea20_OpenJS-Foundation-Bylaws-2023-09-18.pdf) will be handled in collaboration with the other two bodies, facilitated by the TSC representative on the CPC. If a Node.js-specific communication channel, such as a social media account or a discussion forum, is established by another party and used to represent the technical work or the technical community of the project, the TSC may request administrator or moderator access to ensure representation is aligned with the consensus within the project. Day-to-day operation in such channels can be delegated to another party as long as they follow the Code of Conduct, and respect the consensus seeking process before representation of the project is manifested. From ec7ff6e0c21faa3707a2d1872e977628f864a819 Mon Sep 17 00:00:00 2001 From: Darshan Sen Date: Thu, 3 Jul 2025 09:19:27 +0530 Subject: [PATCH 18/20] Update TSC-Charter.md Co-authored-by: Joyee Cheung --- TSC-Charter.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index 760a07c2..fe53f637 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -74,7 +74,15 @@ including: * Development process and any coding standards. * Mediating technical conflicts between Collaborators or Foundation projects. -* Establishing and stewarding a consensus-seeking process to represent the technical community and its work in external communications. +* Establishing and stewarding a consensus-seeking process to represent the technical community and its work in external communications. The scope includes: + * Technical development and its process in the the project + * Releases and release announcements + * Technical documentation + * Contributor onboarding and conduct + * Project governance + * Technical direction + * The project website and download server + * Petition from the technical community that can be surfaced to the CPC level The TSC will define Node.js project’s release vehicles. From e2d0b709efeb09a58b5084034519fa13806b37bf Mon Sep 17 00:00:00 2001 From: Darshan Sen Date: Thu, 3 Jul 2025 10:06:20 +0530 Subject: [PATCH 19/20] Update TSC-Charter.md Signed-off-by: Darshan Sen --- TSC-Charter.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index fe53f637..109e8d47 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -86,7 +86,7 @@ including: The TSC will define Node.js project’s release vehicles. -Communication on topics where the scope of the TSC intersects with that of the [OpenJS CPC](https://github.com/openjs-foundation/cross-project-council/blob/main/CPC-CHARTER.md) or the [OpenJS board](https://images.prismic.io/openjsf/c31b195a-83c9-4d89-9d92-d0cb8840ea20_OpenJS-Foundation-Bylaws-2023-09-18.pdf) will be handled in collaboration with the other two bodies, facilitated by the TSC representative on the CPC. +Communication on topics where the scope of the TSC intersects with that of the [OpenJS CPC][] or the [OpenJS board][] will be handled in collaboration with the other two bodies, facilitated by the TSC representative on the CPC. If a Node.js-specific communication channel, such as a social media account or a discussion forum, is established by another party and used to represent the technical work or the technical community of the project, the TSC may request administrator or moderator access to ensure representation is aligned with the consensus within the project. Day-to-day operation in such channels can be delegated to another party as long as they follow the Code of Conduct, and respect the consensus seeking process before representation of the project is manifested. @@ -184,3 +184,5 @@ and Contributors looking to participate in the development effort. [Condorcet]: https://en.wikipedia.org/wiki/Condorcet_method [Consensus Seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making [Single Transferable Vote]: https://en.wikipedia.org/wiki/Single_transferable_vote +[OpenJS CPC]: https://github.com/openjs-foundation/cross-project-council/blob/main/CPC-CHARTER.md +[OpenJS board]: https://images.prismic.io/openjsf/c31b195a-83c9-4d89-9d92-d0cb8840ea20_OpenJS-Foundation-Bylaws-2023-09-18.pdf From 35266acbad6fb8761c203ddceed53e4725cc7451 Mon Sep 17 00:00:00 2001 From: Darshan Sen Date: Thu, 3 Jul 2025 16:48:42 +0530 Subject: [PATCH 20/20] Update TSC-Charter.md Signed-off-by: Darshan Sen --- TSC-Charter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TSC-Charter.md b/TSC-Charter.md index 109e8d47..27d24f31 100755 --- a/TSC-Charter.md +++ b/TSC-Charter.md @@ -183,6 +183,6 @@ and Contributors looking to participate in the development effort. [Condorcet]: https://en.wikipedia.org/wiki/Condorcet_method [Consensus Seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making -[Single Transferable Vote]: https://en.wikipedia.org/wiki/Single_transferable_vote [OpenJS CPC]: https://github.com/openjs-foundation/cross-project-council/blob/main/CPC-CHARTER.md [OpenJS board]: https://images.prismic.io/openjsf/c31b195a-83c9-4d89-9d92-d0cb8840ea20_OpenJS-Foundation-Bylaws-2023-09-18.pdf +[Single Transferable Vote]: https://en.wikipedia.org/wiki/Single_transferable_vote