From 0cc25d9ab8e5fe8d2a11111b432c8be7a91ea588 Mon Sep 17 00:00:00 2001 From: AayushSaini101 Date: Tue, 9 Apr 2024 17:23:51 +0530 Subject: [PATCH 01/19] Added voting.md file --- voting.md | 44 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 voting.md diff --git a/voting.md b/voting.md new file mode 100644 index 000000000..14c933574 --- /dev/null +++ b/voting.md @@ -0,0 +1,44 @@ +## Overview + +In the [search for the right governance model](https://www.asyncapi.com/blog/governance-motivation) we ended up defining Technical Steering Committee (TSC) that can help making decisions that are related to entire AsyncAPI Initiative and not only specific repository. TSC voting is described in official [Charter](https://github.com/asyncapi/community/blob/master/CHARTER.md#4-tsc-voting). + +To make voting process easier with proper automation we use [**git-vote**](https://github.com/cncf/gitvote) bot. +### Voting Location + +- Voting must take place only in [community](https://github.com/asyncapi/community) repository +- Voting automation works only with GitHub Issues and Pull Requests + +Discussions should be used only for initial discussion, to brainstorm ideas or get some initial support. + +In majority of cases topics we vote on introduce some new rules, some new ways of doing things. This means that in majority of cases the topic we vote on needs proper community documentation. We recommend that you use Pull Requests over Issues to run voting on topic where you provide context and final documentation. + +### Voting Rules + +* Only votes from [TSC members](https://www.asyncapi.com/community/tsc) are counted. You are still encouraged to participate in voting, even if your vote is not binding. +* TSC members have no less than 7 calendar days to vote. As community we did not set exact voting deadline and only have a rule that you can translate into: "just be nice and give people at least 7 days to get familiar with the topic so they can vote". Our automation is set for 4 weeks, to take into account all possible limitations related to holidays and other events. +* The vote completes when more than 50% voting are in favour. + +### Voting Process + +#### Start Voting + +1. TSC member adds `/vote` comment to an Issue or a Pull Request. +2. Git Vote bot creates a comment with instruction on how the voting should be done. It is based on πŸ‘πŸΌ , πŸ‘ŽπŸΌ and πŸ‘€ emojis. You can still put comments or suggestions. +3. AsyncAPI bot adds `vote` label so later it is easier for us to extract information about voted topics and participation. + +#### Check Status + +1. Anyone can add `/check-vote` comment to an Issue or a Pull Request. +2. Git Vote bot creates a comment with update on how many binding votes were provided and how much is missing to reach the quorum. + +### Cancel Voting + +1. TSC member adds `/cancel-vote` comment to an Issue or a Pull Request. +2. Git Vote bot creates a comment. +3. AsyncAPI bot removes `vote` label. + +### Finish Voting + +There is no way to complete voting with a comment. It ends either when quorum is reached or duration deadline ends. + +Git Vote bot adds a comment that voting is completed. From 07e443fb4debff7411c49e62c5e36e1bd58abacc Mon Sep 17 00:00:00 2001 From: Zack_Aayush <60972989+AayushSaini101@users.noreply.github.com> Date: Wed, 10 Apr 2024 15:26:47 +0530 Subject: [PATCH 02/19] Update voting.md Co-authored-by: Sergio Moya <1083296+smoya@users.noreply.github.com> --- voting.md | 1 + 1 file changed, 1 insertion(+) diff --git a/voting.md b/voting.md index 14c933574..dfbc3afc1 100644 --- a/voting.md +++ b/voting.md @@ -3,6 +3,7 @@ In the [search for the right governance model](https://www.asyncapi.com/blog/governance-motivation) we ended up defining Technical Steering Committee (TSC) that can help making decisions that are related to entire AsyncAPI Initiative and not only specific repository. TSC voting is described in official [Charter](https://github.com/asyncapi/community/blob/master/CHARTER.md#4-tsc-voting). To make voting process easier with proper automation we use [**git-vote**](https://github.com/cncf/gitvote) bot. + ### Voting Location - Voting must take place only in [community](https://github.com/asyncapi/community) repository From fe6c3b0b4a57c4973dd5b006c79fc241e22242e4 Mon Sep 17 00:00:00 2001 From: AayushSaini101 Date: Wed, 10 Apr 2024 16:20:38 +0530 Subject: [PATCH 03/19] Update voting doc --- voting.md | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/voting.md b/voting.md index dfbc3afc1..268d4657a 100644 --- a/voting.md +++ b/voting.md @@ -1,45 +1,45 @@ ## Overview -In the [search for the right governance model](https://www.asyncapi.com/blog/governance-motivation) we ended up defining Technical Steering Committee (TSC) that can help making decisions that are related to entire AsyncAPI Initiative and not only specific repository. TSC voting is described in official [Charter](https://github.com/asyncapi/community/blob/master/CHARTER.md#4-tsc-voting). +In the [search for the right governance model](https://www.asyncapi.com/blog/governance-motivation) we ended up defining a Technical Steering Committee (TSC) that can help make decisions that are related to the entire AsyncAPI Initiative and not only a specific repository. TSC voting is described in the official [Charter](https://github.com/asyncapi/community/blob/master/CHARTER.md#4-tsc-voting). -To make voting process easier with proper automation we use [**git-vote**](https://github.com/cncf/gitvote) bot. +To make the voting process easier with proper automation we use [**git-vote**](https://github.com/cncf/gitvote) bot. ### Voting Location - Voting must take place only in [community](https://github.com/asyncapi/community) repository - Voting automation works only with GitHub Issues and Pull Requests -Discussions should be used only for initial discussion, to brainstorm ideas or get some initial support. +Discussions should be used only for initial discussion, to brainstorm ideas or to get some initial support. -In majority of cases topics we vote on introduce some new rules, some new ways of doing things. This means that in majority of cases the topic we vote on needs proper community documentation. We recommend that you use Pull Requests over Issues to run voting on topic where you provide context and final documentation. +In the majority of cases topics we vote on introduce some new rules, some new ways of doing things. This means that in the majority of cases, the topic we vote on needs proper community documentation. We recommend that you use Pull Requests over Issues to run voting on a topic where you provide context and final documentation. ### Voting Rules * Only votes from [TSC members](https://www.asyncapi.com/community/tsc) are counted. You are still encouraged to participate in voting, even if your vote is not binding. -* TSC members have no less than 7 calendar days to vote. As community we did not set exact voting deadline and only have a rule that you can translate into: "just be nice and give people at least 7 days to get familiar with the topic so they can vote". Our automation is set for 4 weeks, to take into account all possible limitations related to holidays and other events. -* The vote completes when more than 50% voting are in favour. +* TSC members have no less than 7 calendar days to vote. As a community, we did not set an exact voting deadline and only have a rule that you can translate into: "Just be nice and give people at least 7 days to get familiar with the topic so they can vote". Our automation is set for 4 weeks, to take into account all possible limitations related to holidays and other events. +* The vote is completed when more than 50% voting are in favour. ### Voting Process #### Start Voting 1. TSC member adds `/vote` comment to an Issue or a Pull Request. -2. Git Vote bot creates a comment with instruction on how the voting should be done. It is based on πŸ‘πŸΌ , πŸ‘ŽπŸΌ and πŸ‘€ emojis. You can still put comments or suggestions. -3. AsyncAPI bot adds `vote` label so later it is easier for us to extract information about voted topics and participation. +2. The Git Vote bot creates a comment with instructions on how the voting should be done. It is based on πŸ‘πŸΌ , πŸ‘ŽπŸΌ and πŸ‘€ emojis. You can still put comments or suggestions. +3. AsyncAPI bot adds a `vote` label so later it is easier for us to extract information about voted topics and participation. #### Check Status -1. Anyone can add `/check-vote` comment to an Issue or a Pull Request. -2. Git Vote bot creates a comment with update on how many binding votes were provided and how much is missing to reach the quorum. +1. Anyone can add a `/check-vote` comment to an Issue or a Pull Request. +2. The Git Vote bot creates a comment with an update on how many binding votes were provided and how much is missing to reach the quorum. ### Cancel Voting 1. TSC member adds `/cancel-vote` comment to an Issue or a Pull Request. -2. Git Vote bot creates a comment. -3. AsyncAPI bot removes `vote` label. +2. The Git Vote bot creates a comment. +3. The AsyncAPI bot removes the `vote` label. ### Finish Voting -There is no way to complete voting with a comment. It ends either when quorum is reached or duration deadline ends. +There is no way to complete voting with a comment. It ends either when the majority of the positive voting is reached that is least 51% of the users with binding votes or the duration deadline ends. -Git Vote bot adds a comment that voting is completed. +The Git Vote bot adds a comment that voting is completed. \ No newline at end of file From 4afd81c2e252b47b0e7250f223eb6b4c642747ef Mon Sep 17 00:00:00 2001 From: Zack_Aayush <60972989+AayushSaini101@users.noreply.github.com> Date: Wed, 10 Apr 2024 17:09:54 +0530 Subject: [PATCH 04/19] Update voting.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Fran MΓ©ndez --- voting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/voting.md b/voting.md index 268d4657a..f2a67c558 100644 --- a/voting.md +++ b/voting.md @@ -40,6 +40,6 @@ In the majority of cases topics we vote on introduce some new rules, some new wa ### Finish Voting -There is no way to complete voting with a comment. It ends either when the majority of the positive voting is reached that is least 51% of the users with binding votes or the duration deadline ends. +There is no way to complete voting with a comment. It ends either when the majority of the positive voting is reached that is least >50% of the users with binding votes or the duration deadline ends. The Git Vote bot adds a comment that voting is completed. \ No newline at end of file From a6fac7e3aafa7ae223376d1ed27d9a8631eccefe Mon Sep 17 00:00:00 2001 From: Zack_Aayush <60972989+AayushSaini101@users.noreply.github.com> Date: Thu, 11 Apr 2024 07:14:46 +0530 Subject: [PATCH 05/19] Update voting.md Co-authored-by: Quetzalli --- voting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/voting.md b/voting.md index f2a67c558..e96906c89 100644 --- a/voting.md +++ b/voting.md @@ -6,7 +6,7 @@ To make the voting process easier with proper automation we use [**git-vote**](h ### Voting Location -- Voting must take place only in [community](https://github.com/asyncapi/community) repository +- Voting must only take place in the [community](https://github.com/asyncapi/community) repository. - Voting automation works only with GitHub Issues and Pull Requests Discussions should be used only for initial discussion, to brainstorm ideas or to get some initial support. From 95b81aa13fd7c586b7f76ced0f7bef08b5d9c83a Mon Sep 17 00:00:00 2001 From: Zack_Aayush <60972989+AayushSaini101@users.noreply.github.com> Date: Thu, 11 Apr 2024 07:15:11 +0530 Subject: [PATCH 06/19] Update voting.md Co-authored-by: Quetzalli --- voting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/voting.md b/voting.md index e96906c89..1bbcbd39e 100644 --- a/voting.md +++ b/voting.md @@ -23,7 +23,7 @@ In the majority of cases topics we vote on introduce some new rules, some new wa #### Start Voting -1. TSC member adds `/vote` comment to an Issue or a Pull Request. +1. TSC member adds a `/vote` comment to an Issue or a Pull Request. 2. The Git Vote bot creates a comment with instructions on how the voting should be done. It is based on πŸ‘πŸΌ , πŸ‘ŽπŸΌ and πŸ‘€ emojis. You can still put comments or suggestions. 3. AsyncAPI bot adds a `vote` label so later it is easier for us to extract information about voted topics and participation. From 1240bd73075b1317d3320926062ed96647e44c23 Mon Sep 17 00:00:00 2001 From: Zack_Aayush <60972989+AayushSaini101@users.noreply.github.com> Date: Thu, 11 Apr 2024 07:15:28 +0530 Subject: [PATCH 07/19] Update voting.md Co-authored-by: Quetzalli --- voting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/voting.md b/voting.md index 1bbcbd39e..b8b1d33ea 100644 --- a/voting.md +++ b/voting.md @@ -7,7 +7,7 @@ To make the voting process easier with proper automation we use [**git-vote**](h ### Voting Location - Voting must only take place in the [community](https://github.com/asyncapi/community) repository. -- Voting automation works only with GitHub Issues and Pull Requests +- Voting automation works only with GitHub Issues and Pull Requests. Discussions should be used only for initial discussion, to brainstorm ideas or to get some initial support. From 4292db266a4f95d7a514598fd0179b90389f33bf Mon Sep 17 00:00:00 2001 From: Zack_Aayush <60972989+AayushSaini101@users.noreply.github.com> Date: Thu, 11 Apr 2024 07:15:40 +0530 Subject: [PATCH 08/19] Update voting.md Co-authored-by: Quetzalli --- voting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/voting.md b/voting.md index b8b1d33ea..427a4b7b4 100644 --- a/voting.md +++ b/voting.md @@ -34,7 +34,7 @@ In the majority of cases topics we vote on introduce some new rules, some new wa ### Cancel Voting -1. TSC member adds `/cancel-vote` comment to an Issue or a Pull Request. +1. The TSC member adds `/cancel-vote` comment to an Issue or a Pull Request. 2. The Git Vote bot creates a comment. 3. The AsyncAPI bot removes the `vote` label. From 7bd2ed48f97601500880e3337c12b8e890d9d665 Mon Sep 17 00:00:00 2001 From: Zack_Aayush <60972989+AayushSaini101@users.noreply.github.com> Date: Thu, 11 Apr 2024 07:15:54 +0530 Subject: [PATCH 09/19] Update voting.md Co-authored-by: Quetzalli --- voting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/voting.md b/voting.md index 427a4b7b4..f58134d50 100644 --- a/voting.md +++ b/voting.md @@ -25,7 +25,7 @@ In the majority of cases topics we vote on introduce some new rules, some new wa 1. TSC member adds a `/vote` comment to an Issue or a Pull Request. 2. The Git Vote bot creates a comment with instructions on how the voting should be done. It is based on πŸ‘πŸΌ , πŸ‘ŽπŸΌ and πŸ‘€ emojis. You can still put comments or suggestions. -3. AsyncAPI bot adds a `vote` label so later it is easier for us to extract information about voted topics and participation. +3. The AsyncAPI bot adds a `vote` label making it easier for us to extract information about voted topics and participation. #### Check Status From 697099b1a3d8a248f0d7b87bfe4697a7fe8ea847 Mon Sep 17 00:00:00 2001 From: Zack_Aayush <60972989+AayushSaini101@users.noreply.github.com> Date: Thu, 11 Apr 2024 17:16:39 +0530 Subject: [PATCH 10/19] Update voting.md Co-authored-by: Lukasz Gornicki --- voting.md | 1 + 1 file changed, 1 insertion(+) diff --git a/voting.md b/voting.md index f58134d50..9ef4066c7 100644 --- a/voting.md +++ b/voting.md @@ -17,6 +17,7 @@ In the majority of cases topics we vote on introduce some new rules, some new wa * Only votes from [TSC members](https://www.asyncapi.com/community/tsc) are counted. You are still encouraged to participate in voting, even if your vote is not binding. * TSC members have no less than 7 calendar days to vote. As a community, we did not set an exact voting deadline and only have a rule that you can translate into: "Just be nice and give people at least 7 days to get familiar with the topic so they can vote". Our automation is set for 4 weeks, to take into account all possible limitations related to holidays and other events. +* TSC members can skip some votes, although, if you do not have an opinion, please participate with πŸ‘€ to indicated that you saw a vote, but you have no opinion and abstain. There is one strict rule though, that if you do not participate in voting within any three-month period, you stop being TSC member. It has nothing to do though with your maintainer responsibilities. * The vote is completed when more than 50% voting are in favour. ### Voting Process From 175319e6dddcf61f38d7faebf065c22eb5c06326 Mon Sep 17 00:00:00 2001 From: AayushSaini101 Date: Fri, 12 Apr 2024 08:11:55 +0530 Subject: [PATCH 11/19] Update voting doc --- voting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/voting.md b/voting.md index 9ef4066c7..cd801acfa 100644 --- a/voting.md +++ b/voting.md @@ -31,7 +31,7 @@ In the majority of cases topics we vote on introduce some new rules, some new wa #### Check Status 1. Anyone can add a `/check-vote` comment to an Issue or a Pull Request. -2. The Git Vote bot creates a comment with an update on how many binding votes were provided and how much is missing to reach the quorum. +2. The Git Vote bot creates a comment with an update on how many binding votes were provided and how much is missing to reach the passing threshold that is at least >50% of the TSC members. ### Cancel Voting From 647d2f70235fa278372454c2fa46fb55ea6ce8cf Mon Sep 17 00:00:00 2001 From: AayushSaini101 Date: Mon, 15 Apr 2024 16:12:18 +0530 Subject: [PATCH 12/19] Improve suggestions --- voting.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/voting.md b/voting.md index cd801acfa..fd2b3d61b 100644 --- a/voting.md +++ b/voting.md @@ -31,7 +31,7 @@ In the majority of cases topics we vote on introduce some new rules, some new wa #### Check Status 1. Anyone can add a `/check-vote` comment to an Issue or a Pull Request. -2. The Git Vote bot creates a comment with an update on how many binding votes were provided and how much is missing to reach the passing threshold that is at least >50% of the TSC members. +2. The Git Vote bot creates a comment with an update on how many binding votes were provided. and how much the percentage requires to finish the voting process. ### Cancel Voting @@ -43,4 +43,10 @@ In the majority of cases topics we vote on introduce some new rules, some new wa There is no way to complete voting with a comment. It ends either when the majority of the positive voting is reached that is least >50% of the users with binding votes or the duration deadline ends. -The Git Vote bot adds a comment that voting is completed. \ No newline at end of file +The Git Vote bot adds a comment that voting is completed. + +### Note + +* As per the CHARTER, quorum is not needed. However, git-vote has technically limitations and quorum should be reached. That's the reason we give 4 weeks to vote and we should chase people to vote in order to reach the quorum of people (people voting is >50). +* The abstain votes are included in the total number of votes, they are not removed. +* At present, the git-vote is enabled in the community repo only, and all the voting process will be done by git-vote bot, We will add git-vote feature in other projects as well in future. From 70de86e41c2874b31b021d495995135f8a0a5282 Mon Sep 17 00:00:00 2001 From: Zack_Aayush <60972989+AayushSaini101@users.noreply.github.com> Date: Mon, 15 Apr 2024 16:19:36 +0530 Subject: [PATCH 13/19] Update voting.md Co-authored-by: Sergio Moya <1083296+smoya@users.noreply.github.com> --- voting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/voting.md b/voting.md index fd2b3d61b..1c247a82f 100644 --- a/voting.md +++ b/voting.md @@ -47,6 +47,6 @@ The Git Vote bot adds a comment that voting is completed. ### Note -* As per the CHARTER, quorum is not needed. However, git-vote has technically limitations and quorum should be reached. That's the reason we give 4 weeks to vote and we should chase people to vote in order to reach the quorum of people (people voting is >50). +* As per the [charter](./CHARTER.md), quorum is not needed. However, git-vote has technical limitations, and a quorum should be reached. That's why we allocate 4 weeks for voting, and it's important to actively encourage participation to ensure that the quorum (where votes cast exceed 50% of eligible voters) is met * The abstain votes are included in the total number of votes, they are not removed. * At present, the git-vote is enabled in the community repo only, and all the voting process will be done by git-vote bot, We will add git-vote feature in other projects as well in future. From 992639594bb522c94370f1096a920b6000ddef9b Mon Sep 17 00:00:00 2001 From: AayushSaini101 Date: Mon, 15 Apr 2024 16:24:04 +0530 Subject: [PATCH 14/19] Rephrase git-vote to Git Vote --- voting.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/voting.md b/voting.md index 1c247a82f..870bf7bac 100644 --- a/voting.md +++ b/voting.md @@ -2,7 +2,7 @@ In the [search for the right governance model](https://www.asyncapi.com/blog/governance-motivation) we ended up defining a Technical Steering Committee (TSC) that can help make decisions that are related to the entire AsyncAPI Initiative and not only a specific repository. TSC voting is described in the official [Charter](https://github.com/asyncapi/community/blob/master/CHARTER.md#4-tsc-voting). -To make the voting process easier with proper automation we use [**git-vote**](https://github.com/cncf/gitvote) bot. +To make the voting process easier with proper automation we use [**Git Vote**](https://github.com/cncf/gitvote) bot. ### Voting Location @@ -47,6 +47,6 @@ The Git Vote bot adds a comment that voting is completed. ### Note -* As per the [charter](./CHARTER.md), quorum is not needed. However, git-vote has technical limitations, and a quorum should be reached. That's why we allocate 4 weeks for voting, and it's important to actively encourage participation to ensure that the quorum (where votes cast exceed 50% of eligible voters) is met +* As per the [charter](./CHARTER.md), quorum is not needed. However, Git Vote has technical limitations, and a quorum should be reached. That's why we allocate 4 weeks for voting, and it's important to actively encourage participation to ensure that the quorum (where votes cast exceed 50% of eligible voters) is met * The abstain votes are included in the total number of votes, they are not removed. -* At present, the git-vote is enabled in the community repo only, and all the voting process will be done by git-vote bot, We will add git-vote feature in other projects as well in future. +* At present, the Git Vote is enabled in the community repo only, and all the voting process will be done by Git Vote bot, We will add Git Vote in other projects as well in the future. From 76991ab816d6a927cb088560205710eb11032559 Mon Sep 17 00:00:00 2001 From: Zack_Aayush <60972989+AayushSaini101@users.noreply.github.com> Date: Mon, 15 Apr 2024 16:25:26 +0530 Subject: [PATCH 15/19] Update voting.md Co-authored-by: Sergio Moya <1083296+smoya@users.noreply.github.com> --- voting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/voting.md b/voting.md index 870bf7bac..992f6bba4 100644 --- a/voting.md +++ b/voting.md @@ -41,7 +41,7 @@ In the majority of cases topics we vote on introduce some new rules, some new wa ### Finish Voting -There is no way to complete voting with a comment. It ends either when the majority of the positive voting is reached that is least >50% of the users with binding votes or the duration deadline ends. +Voting cannot be concluded with a comment; it ends when either more than half of the users with binding votes say yes, or when the deadline passes. The Git Vote bot adds a comment that voting is completed. From 5e44df16a84fdc01d29be0f84382db5510955bf3 Mon Sep 17 00:00:00 2001 From: Zack_Aayush <60972989+AayushSaini101@users.noreply.github.com> Date: Thu, 18 Apr 2024 11:02:43 +0530 Subject: [PATCH 16/19] Update voting.md --- voting.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/voting.md b/voting.md index 992f6bba4..47044df0c 100644 --- a/voting.md +++ b/voting.md @@ -9,15 +9,15 @@ To make the voting process easier with proper automation we use [**Git Vote**](h - Voting must only take place in the [community](https://github.com/asyncapi/community) repository. - Voting automation works only with GitHub Issues and Pull Requests. -Discussions should be used only for initial discussion, to brainstorm ideas or to get some initial support. +The Discussions should only be used for initial discussion, brainstorming ideas, or seeking initial support. -In the majority of cases topics we vote on introduce some new rules, some new ways of doing things. This means that in the majority of cases, the topic we vote on needs proper community documentation. We recommend that you use Pull Requests over Issues to run voting on a topic where you provide context and final documentation. +In the majority of cases, topics we vote on introduce new rules or ways of doing things. This implies that proper community documentation is needed for the topics we vote on. We recommend using Pull Requests instead of Issues to conduct voting on a topic, as it allows you to provide context and finalize documentation. ### Voting Rules * Only votes from [TSC members](https://www.asyncapi.com/community/tsc) are counted. You are still encouraged to participate in voting, even if your vote is not binding. * TSC members have no less than 7 calendar days to vote. As a community, we did not set an exact voting deadline and only have a rule that you can translate into: "Just be nice and give people at least 7 days to get familiar with the topic so they can vote". Our automation is set for 4 weeks, to take into account all possible limitations related to holidays and other events. -* TSC members can skip some votes, although, if you do not have an opinion, please participate with πŸ‘€ to indicated that you saw a vote, but you have no opinion and abstain. There is one strict rule though, that if you do not participate in voting within any three-month period, you stop being TSC member. It has nothing to do though with your maintainer responsibilities. +* TSC members can skip some votes, although, if you do not have an opinion, please participate with πŸ‘€ to indicate that you saw a vote, but you have no opinion and abstain. There is one strict rule though, that if you do not participate in voting within any three-month period, you stop being a TSC member. It has nothing to do though with your maintainer responsibilities. * The vote is completed when more than 50% voting are in favour. ### Voting Process @@ -31,7 +31,7 @@ In the majority of cases topics we vote on introduce some new rules, some new wa #### Check Status 1. Anyone can add a `/check-vote` comment to an Issue or a Pull Request. -2. The Git Vote bot creates a comment with an update on how many binding votes were provided. and how much the percentage requires to finish the voting process. +2. The Git Vote bot creates a comment with an update on how many binding votes were provided. and how much the percentage is required to finish the voting process. ### Cancel Voting @@ -49,4 +49,4 @@ The Git Vote bot adds a comment that voting is completed. * As per the [charter](./CHARTER.md), quorum is not needed. However, Git Vote has technical limitations, and a quorum should be reached. That's why we allocate 4 weeks for voting, and it's important to actively encourage participation to ensure that the quorum (where votes cast exceed 50% of eligible voters) is met * The abstain votes are included in the total number of votes, they are not removed. -* At present, the Git Vote is enabled in the community repo only, and all the voting process will be done by Git Vote bot, We will add Git Vote in other projects as well in the future. +* At present, the Git Vote is enabled in the community repo only, and all the voting processes will be done by the Git Vote bot, We will add Git Vote in other projects as well in the future. From 4f28b95a7d861b8b290f78248dca9a1a036613bd Mon Sep 17 00:00:00 2001 From: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> Date: Thu, 18 Apr 2024 10:59:01 +0200 Subject: [PATCH 17/19] punctuation correction --- voting.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/voting.md b/voting.md index 47044df0c..cd47e0553 100644 --- a/voting.md +++ b/voting.md @@ -1,8 +1,8 @@ ## Overview -In the [search for the right governance model](https://www.asyncapi.com/blog/governance-motivation) we ended up defining a Technical Steering Committee (TSC) that can help make decisions that are related to the entire AsyncAPI Initiative and not only a specific repository. TSC voting is described in the official [Charter](https://github.com/asyncapi/community/blob/master/CHARTER.md#4-tsc-voting). +In the [search for the right governance model](https://www.asyncapi.com/blog/governance-motivation), we ended up defining a Technical Steering Committee (TSC) that can help make decisions related to the entire AsyncAPI Initiative and not only a specific repository. TSC voting is described in the official [Charter](https://github.com/asyncapi/community/blob/master/CHARTER.md#4-tsc-voting). -To make the voting process easier with proper automation we use [**Git Vote**](https://github.com/cncf/gitvote) bot. +To make the voting process easier with proper automation, we use [**Git Vote**](https://github.com/cncf/gitvote) bot. ### Voting Location @@ -11,14 +11,14 @@ To make the voting process easier with proper automation we use [**Git Vote**](h The Discussions should only be used for initial discussion, brainstorming ideas, or seeking initial support. -In the majority of cases, topics we vote on introduce new rules or ways of doing things. This implies that proper community documentation is needed for the topics we vote on. We recommend using Pull Requests instead of Issues to conduct voting on a topic, as it allows you to provide context and finalize documentation. +In the majority of cases, topics we vote on introduce new rules or ways of doing things. This implies that proper community documentation is needed for these topics. We recommend using Pull Requests instead of Issues to conduct voting on a topic, as it allows you to provide context and finalize documentation. ### Voting Rules * Only votes from [TSC members](https://www.asyncapi.com/community/tsc) are counted. You are still encouraged to participate in voting, even if your vote is not binding. -* TSC members have no less than 7 calendar days to vote. As a community, we did not set an exact voting deadline and only have a rule that you can translate into: "Just be nice and give people at least 7 days to get familiar with the topic so they can vote". Our automation is set for 4 weeks, to take into account all possible limitations related to holidays and other events. -* TSC members can skip some votes, although, if you do not have an opinion, please participate with πŸ‘€ to indicate that you saw a vote, but you have no opinion and abstain. There is one strict rule though, that if you do not participate in voting within any three-month period, you stop being a TSC member. It has nothing to do though with your maintainer responsibilities. -* The vote is completed when more than 50% voting are in favour. +* TSC members have at least 7 calendar days to vote. As a community, we did not set an exact voting deadline and only have a rule that you can translate into: "Just be nice and give people at least 7 days to get familiar with the topic so they can vote." Our automation is set for 4 weeks to take into account all possible limitations related to holidays and other events. +* TSC members can skip some votes, although, if you do not have an opinion, please participate with πŸ‘€ to indicate that you saw a vote but you have no opinion and abstain. There is one strict rule, though: if you do not participate in voting within three months, you will stop being a TSC member. It has nothing to do, though, with your maintainer responsibilities. +* The vote is completed when more than 50% of the voting is in favor. ### Voting Process @@ -26,12 +26,12 @@ In the majority of cases, topics we vote on introduce new rules or ways of doing 1. TSC member adds a `/vote` comment to an Issue or a Pull Request. 2. The Git Vote bot creates a comment with instructions on how the voting should be done. It is based on πŸ‘πŸΌ , πŸ‘ŽπŸΌ and πŸ‘€ emojis. You can still put comments or suggestions. -3. The AsyncAPI bot adds a `vote` label making it easier for us to extract information about voted topics and participation. +3. The AsyncAPI bot adds a `vote` label, making it easier to extract information about voted topics and participation. #### Check Status 1. Anyone can add a `/check-vote` comment to an Issue or a Pull Request. -2. The Git Vote bot creates a comment with an update on how many binding votes were provided. and how much the percentage is required to finish the voting process. +2. The Git Vote bot creates a comment with an update on how many binding votes were provided. And how much the percentage is required to finish the voting process. ### Cancel Voting @@ -41,12 +41,12 @@ In the majority of cases, topics we vote on introduce new rules or ways of doing ### Finish Voting -Voting cannot be concluded with a comment; it ends when either more than half of the users with binding votes say yes, or when the deadline passes. +Voting cannot be concluded with a comment; it ends when more than half of the users with binding votes say yes or when the deadline passes. The Git Vote bot adds a comment that voting is completed. ### Note -* As per the [charter](./CHARTER.md), quorum is not needed. However, Git Vote has technical limitations, and a quorum should be reached. That's why we allocate 4 weeks for voting, and it's important to actively encourage participation to ensure that the quorum (where votes cast exceed 50% of eligible voters) is met -* The abstain votes are included in the total number of votes, they are not removed. -* At present, the Git Vote is enabled in the community repo only, and all the voting processes will be done by the Git Vote bot, We will add Git Vote in other projects as well in the future. +* As per the [Charter] (./CHARTER.md), a quorum is not needed. However, Git Vote has technical limitations, and a quorum should be reached. That's why we allocate 4 weeks for voting, and it's important to actively encourage participation to ensure that the quorum (where votes cast exceed 50% of eligible voters) is met. +* The abstain votes are included in the total number of votes; they are not removed. +* At present, Git Vote is enabled in the community repo only, and the Git Vote bot handles all voting processes. We will add Git Vote to other projects in the future. From e3e42c3d512c8475ae49fa4b34b2b338240cb706 Mon Sep 17 00:00:00 2001 From: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> Date: Thu, 18 Apr 2024 11:02:18 +0200 Subject: [PATCH 18/19] Update voting.md --- voting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/voting.md b/voting.md index cd47e0553..d3fe8e829 100644 --- a/voting.md +++ b/voting.md @@ -47,6 +47,6 @@ The Git Vote bot adds a comment that voting is completed. ### Note -* As per the [Charter] (./CHARTER.md), a quorum is not needed. However, Git Vote has technical limitations, and a quorum should be reached. That's why we allocate 4 weeks for voting, and it's important to actively encourage participation to ensure that the quorum (where votes cast exceed 50% of eligible voters) is met. +* As per the [Charter](./CHARTER.md), a quorum is not needed. However, Git Vote has technical limitations, and a quorum should be reached. That's why we allocate 4 weeks for voting, and it's important to actively encourage participation to ensure that the quorum (where votes cast exceed 50% of eligible voters) is met. * The abstain votes are included in the total number of votes; they are not removed. * At present, Git Vote is enabled in the community repo only, and the Git Vote bot handles all voting processes. We will add Git Vote to other projects in the future. From 1b7d67b992f6d872bb749b694badf8e3b004175e Mon Sep 17 00:00:00 2001 From: Zack_Aayush <60972989+AayushSaini101@users.noreply.github.com> Date: Fri, 19 Apr 2024 15:10:25 +0530 Subject: [PATCH 19/19] Update voting.md Co-authored-by: Sergio Moya <1083296+smoya@users.noreply.github.com> --- voting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/voting.md b/voting.md index d3fe8e829..b2d3e71e0 100644 --- a/voting.md +++ b/voting.md @@ -24,7 +24,7 @@ In the majority of cases, topics we vote on introduce new rules or ways of doing #### Start Voting -1. TSC member adds a `/vote` comment to an Issue or a Pull Request. +1. The TSC member adds a `/vote` comment to an Issue or a Pull Request. 2. The Git Vote bot creates a comment with instructions on how the voting should be done. It is based on πŸ‘πŸΌ , πŸ‘ŽπŸΌ and πŸ‘€ emojis. You can still put comments or suggestions. 3. The AsyncAPI bot adds a `vote` label, making it easier to extract information about voted topics and participation.