On Thu, 2020-11-12 at 15:06 +0100, Kamil Paral wrote: > Hello, > some of you used the Blockerbugs discussion tickets during the F33 cycle. > I'd love to have your feedback on that functionality. > > As a refresher, those discussion tickets are available from the Blockerbugs > website [1] after clicking on Vote/Discuss links, which forward you to a > ticket available in the blocker-review project [2] on Pagure. In such a > ticket, anyone can vote on blocker bug/freeze exception status of that > particular bug (an example [3]). > > These discussion tickets were created to shorten our regular IRC blocker > meetings and allow people to submit their opinions and votes outside of the > meeting hours. > > *I'd like to know how well it worked, in your opinion.* > > I'd like to learn whether these discussion tickets were a worthwhile > addition to the blockerbugs process, and in case they were, then identify > pain points, annoyances and bugs so that we can improve them. > > So, please reply with anything that's on your heart regarding this topic. > Here are a few suggestions of topics to think over: > * Does it make sense to keep blockerbugs discussion tickets? > * Does it make sense to keep blockerbugs IRC meetings? > * What is your general opinion on discussion tickets, do you like > it/dislike it/don't care? > * Did you find any annoyances or have any pet peeves with discussion > tickets? > * What would you like to see improved in those discussion tickets or in > their integration with Blockerbugs and Bugzilla websites? > > Thanks a lot for your thoughts. 🍪 I think it worked great. It let us process a lot of straightforward decisions without the delay of waiting till the next meeting or the awkwardness of doing it in Bugzilla, and it made the meetings way shorter. By all means let's keep it. My principal issues were really just "quality of life" things: * No synchronization of "decision made" between ticket and Bugzilla, when a decision is made someone has to update both separately (using different Magic Texts, which it's easy to mess up). It would be really nice if we could just mark the decision in Bugzilla and have that automatically propagate to the ticket system. * Using Magic Text for voting and admin is awkward and error-prone. Better UI for this would be really helpful. In addition, the state isn't automatically updated when you vote or mark a decision, so I always find myself manually refreshing the page after doing it just to make sure I did it right and the change took effect. * It'd be really nice if the web UI showed the current vote counts from the ticket. I frequently find myself opening every proposal ticket in a tab and going through them all just to see if any have enough votes for a decision yet; it'd be much more efficient if I could just see the totals at a glance on the blockerbugs web UI overview. That's all the ones I remember for now. Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx 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://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
