docs: add instruction how voting automation works

[AayushSaini101]

Related to #1093

Message from @derberg

We just enabled automation around voting process (using same tool as CNCF). We already enabled it but only to be able to test it now, in this PR as a first automated decision. We can always disable it if we do not reach consensus.

This PR contains documentation on how voting process works. Please have a look and vote or leave a comment if something is not clear or you do not agree with.

There are some changes, like for example no more voting through discussions (technical limitation that imho is not that bad after all)

voting instruction and comment where to leave a vote: #1155 (comment)

[AayushSaini101]

/vote

[git-vote]

Only repository collaborators can create a vote @AayushSaini101.

For organization-owned repositories, the list of collaborators includes outside collaborators, organization members that are direct collaborators, organization members with access through team memberships, organization members with access through default organization permissions, and organization owners.

[asyncapi-bot-eve]

Hi @AayushSaini101, since you are not a TSC Member, you cannot start or stop voting. Please read more about voting process

[AayushSaini101]

/cancel-vote

[asyncapi-bot-eve]

Hi @AayushSaini101, since you are not a TSC Member, you cannot start or stop voting. Please read more about voting process

[derberg]

/vote

[git-vote]

Vote created

@derberg has called for a vote on docs: add instruction how voting automation works (#1155).

The members of the following teams have binding votes:

Team
@asyncapi/tsc_members

Non-binding votes are also appreciated as a sign of support!

How to vote

You can cast your vote by reacting to this comment. The following reactions are supported:

In favor	Against	Abstain
👍	👎	👀

Please note that voting for multiple options is not allowed and those votes won't be counted.

The vote will be open for 28days. It will pass if at least 51% of the users with binding votes vote In favor 👍. Once it's closed, results will be published here as a new comment.

[derberg]

@asyncapi/tsc_members please look at description of this PR and then voting instructions #1155 (comment)

This is a first voting with automation:

Please look on voting.md and if you agree or disagree - vote as per instructions or just ask a comment to clarify instructions

[derberg]

@alequetzalli since your last review there were some sections added, can you please have a look?

[AayushSaini101]

@alequetzalli since your last review there were some sections added, can you please have a look?

@derberg please review :)

[whitlockjc]

👍

[asyncapi-bot]

Hello, @AayushSaini101! 👋🏼
This PR is not up to date with the base branch and can't be merged.
Please update your branch manually with the latest version of the base branch.
PRO-TIP: To request an update from the upstream branch, simply comment /u or /update and our bot will handle the update operation promptly.

       The only requirement for this to work is to enable [Allow edits from maintainers](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork) option in your PR. Also the update will not work if your fork is located in an organization, not under your personal profile.
       Thanks 😄

[AayushSaini101]

@alequetzalli is not active due to some reasons from the last couple of days, also her suggestions resolved in this commit thanks @thulieblack, I also improved a lot and other improvements can be done later if any case find in the doc. :) thanks

[smoya]

@alequetzalli is not active due to some reasons from the last couple of days, also her suggestions resolved in this commit thanks @thulieblack, I also improved a lot and other improvements can be done later if any case find in the doc. :) thanks

Merging is blocked due to @alequetzalli requests.

Unless another owner dismisses it's review, I believe you won't be able to get this PR merged before Alejandra comes back.
My personal opinion: I believe we are not in such a rush and you should wait for Alejandra's approval. But I'm not owner so 🤷

[derberg]

@alequetzalli should we wait for you?

[derberg]

ok, I checked and changes requested by @alequetzalli were addressed. They also do not relate to the core of the PR, so if some text can be done better, and more clear later, there can always be a followup PR.

@AayushSaini101 thanks a lot for the work! There were over 30 votes provided 🚀