I support the idea of an asynchronous blocker bug process.
Blocker Bugs App (DIY solution)
I am not sure how complicated that would be, but the blockerbug application could do the stuff and in the background it could have Bugzilla as a backed, so the Bugzilla process described later, could be controlled from the Blocker Bugs application. This would have a strong stable backend with all pluses and the rather Spartan looks could be replaced by more modern UI of the Fedora Bootstrap.
I would rather avoid this, as this needs a lot of attention, otherwise you might overlook some important part of the communication.
That seems the same to me. Only the medium differs. Maybe, the tagging is a plus for Pagure.
7. People vote by submitting comments containing VOTE +1/0/-1 on a separate line (and including any justification or feedback they wish in the comment as well; the command has to simply be on its own line so that we can detect it well).
The VOTE must be only +1 or -1. Indecisive people do not need to put that down, they just can do nothing.
Otherwise, I think it is ok.
test mailing list -- firstname.lastname@example.org
To unsubscribe send an email to email@example.com
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://firstname.lastname@example.org