On Mon, 2020-11-16 at 20:29 +0100, Kamil Paral wrote: > > > > * Using Magic Text for voting and admin is awkward and error-prone. > > Better UI for this would be really helpful. > > > I'm not sure how it can be improved. Do you have any ideas? Well, by having Pagure provide specific UI for it. Think something like Bodhi update votes. Of course this requires work in Pagure, I guess. > > > 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. > > > > Yes, that's the recommended approach documented at > https://pagure.io/fedora-qa/blocker-review . Pagure can actually detect a > change in description and in theory it should refresh it live, but mostly > I've seen it simply becoming a mess of characters, because while it updated > the contents, it didn't render it as RST and it was just a messy output. I > wanted to file a bug about it, but when I tested it today, it didn't even > respond to description updates and simply nothing happened and I had to > reload the page. So I'm not sure whether it's a race or they fixed the > previous incorrect behavior by simply not responding to that event, > *shrug*. Since Fedora seems to be moving towards Gitlab, I don't want to > spend too much time debugging Pagure issues at the moment. > > With Lukas Brabec we also considered adding a "thumbs up" reaction to your > comment if it contains a well-parsed command, which could show up > immediately. But it seems to be not supported by Pagure API at the moment. > > Do you have some idea how to make the voting process feedback better, > without relying on Pagure bugfixes/feature updates? No. The job would be to fix Pagure. :) IIRC, I get the "mess of characters" result when voting, and the "no auto-refresh at all" result when registering a decision. > > > * 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. > > > > Filed as https://pagure.io/fedora-qa/blockerbugs/issue/150 > > On Thu, Nov 12, 2020 at 9:25 PM Chris Murphy <lists@xxxxxxxxxxxxxxxxx> > wrote: > > > I often had to click the 'how to vote' link in a separate tab to > > copy/paste the proper tag. It'd be nice if the list of possible voting > > tags is simply incorporated into the initial issue text. > > > > Do you mean the list of trackers - BetaBlocker, FinalBlocker, BetaFE, > FinalFE, 0Day, PreviousRelease? I found them quite easy to remember, once > you vote in a few tickets. It's rather harder to keep them straight if you also have to deal with the similar-but-not-quite-the-same Bugzilla magic texts... > I tried to create the tracker names in the same spirit as we use it at IRC > meetings and in Bugzilla (well, in Bugzilla we use FreezeException instead > of FE, but I thought everybody would hate me for making them write long > words in each ticket). FWIW, I chose the long version for Bugzilla because it gives someone who does not already know what an "FE" is a fighting chance of understanding what it means. > At IRC meetings we usually have the order reversed > ("+1 BetaBlocker"), but I swapped it because it was easier to implement > parsing with the tracker name being first, which also seemed more logical > ("BetaBlocker +1"). I would kind of like if the parsing was more permissive. I'd at least expect it to accept any combination in any order of "+1/-1", a valid vote target name, and any amount of whitespace as a valid vote. -- 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
