As part of our Roadmap RFC process, we have a consensus voting process. Currently when we want to use it, it would use the following github action: withstudiocms/roadmap:command.yml
Instead I propose we integrate Artemis to be able to do the following:
- Listen for a consensus request (via command/message on GitHub)
1a. ensure this only runs when no other existing consensus vote exists
1b. Should only be able to be requested by Maintainers
1c. Use reactions on the message as a way to identify if there is an active request
1d. If there is a request with reaction, do nothing as there is already a request being processed.
- Leave a reply on the discussion saying that a request has been made.
2a. Should inform users when to expect a result
2b. Will need a reference stored in a DB table for reference later
- Send said request to discord as a Poll
3a. Poll should contain the following options: Yes, No, Abstain.
3b. Poll should allow for enough time for Maintainers to vote.
3c. Poll should be sent to the correct discord channel.
3d. Poll should reference stored table entry and will likely need some sort of scheduled task? (more research required)
- Once a decision is made (Poll resolution), the final outcome should then be reported back to the discussion by updating the original message.
4a. Use previously stored reference from DB
4b. The outcome should be anonymous (only show numbers, no names)
4c. Remove previous consensus request with reaction in discussion as that will allow future requests.
4d. We don't need to cleanup the vote results as we want those to stay.
This will provide us with an easier way to integrate our voting process with our discord when needed.
As part of our Roadmap RFC process, we have a consensus voting process. Currently when we want to use it, it would use the following github action: withstudiocms/roadmap:command.yml
Instead I propose we integrate Artemis to be able to do the following:
1a. ensure this only runs when no other existing consensus vote exists
1b. Should only be able to be requested by Maintainers
1c. Use reactions on the message as a way to identify if there is an active request
1d. If there is a request with reaction, do nothing as there is already a request being processed.
2a. Should inform users when to expect a result
2b. Will need a reference stored in a DB table for reference later
3a. Poll should contain the following options: Yes, No, Abstain.
3b. Poll should allow for enough time for Maintainers to vote.
3c. Poll should be sent to the correct discord channel.
3d. Poll should reference stored table entry and will likely need some sort of scheduled task? (more research required)
4a. Use previously stored reference from DB
4b. The outcome should be anonymous (only show numbers, no names)
4c. Remove previous consensus request with reaction in discussion as that will allow future requests.
4d. We don't need to cleanup the vote results as we want those to stay.
This will provide us with an easier way to integrate our voting process with our discord when needed.