Integrate git-vote to get better automation around TSC voting and easy to calculate participation

[derberg]

https://github.com/cncf/gitvote is already installed in our organization, for community repo

There is one problem here - I don't think it supports discussions. But also I don't think it is a big problem. We can still use discussions to discuss stuff, and then use PR/issue for final voting, depending on the case.

config for .gitvote.yml that would have to be introduced:

profiles:
  default:
    duration: 2m
    pass_threshold: 51
    periodic_status_check: "1 week"
    allowed_voters:
      teams:
        - tsc_members

outcome should be:

• we need config as above
• we need document that describes how things work, commands and all that stuff
• we need additional workflow that after adding /vote comment, it adds a label to the issue/PR so later it is easier to track record of votes. When /cancel-vote is added, we should remove the label.
• we should also have a workflow that will add vote-passed or vote-did-not-pass whenever git-vote bot adds related comment

[derberg]

workflows should be easy to do as we already have experience with handling in workflow concepts like:

• react to comment
• add label

https://github.com/search?q=repo%3Aasyncapi%2F.github%20comment&type=code

[AayushSaini101]

workflows should be easy to do as we already have experience with handling in workflow concepts like:

• react to comment
• add label

https://github.com/search?q=repo%3Aasyncapi%2F.github%20comment&type=code

@derberg I am interested in this issue, also have experience in workflow in the past we used in the generator issue thanks asyncapi/generator#538

[aeworxet]

Bounty Issue's service comment

Text labels: bounty/2024-Q2, bounty/medium, bounty/devops
First assignment to third-party contributors: 2024-03-22 00:00:00 UTC+12:00
End Of Life: 2024-08-31 23:59:59 UTC-12:00

@asyncapi/bounty_team

[AayushSaini101]

@derberg I have started working on my own repo for testing AayushSaini101/Vote#1 here is the sample, We just need to add configuration for the allowed users and command.

[derberg]

@AayushSaini101 ok, assigned the issue to you. Please go ahead

[Shurtu-gal]

We can have automation around voting too like changes in CODEOWNERS files can call for voting by tsc_members using this

Furthermore, we can have multiple profiles as well:-

• TSC_MEMBER voting
• Community Voting
• Maintainers Voting

WDYT? @derberg

Also, should we add the profile for the whole organisation or just this repo ?

[aeworxet]

Bounty Issue's Timeline

Complexity Level	Assignment date (by GitHub)	Start date (by BP rules)	End date (by BP rules)	Draft PR submission	Final PR submission	Final PR merge
Medium	2024-03-21	2024-04-01	2024-05-10	2024-04-12	2024-04-26	2024-05-10

Please note that the dates given represent deadlines, not specific dates, so if the goal is reached sooner, it's better.

Keep in mind the responsibility for violations of the Timeline.

[derberg]

@Shurtu-gal at the moment we officially have only something like TSC voting

also, codeowners changes are not a subject for voting for TSC but only repo maintainers decision

[derberg]

we still need to get #1155 merged first

[derberg]

@aeworxet fyi bounty completed

[aeworxet]

Bounty Issue Completed 🎉

@AayushSaini101, please go to the AsyncAPI page on Open Collective and submit an invoice for USD 200.00 with the expense title Bounty community#1093, tag bounty, and full URL of this Bounty Issue in the description.