On Sat, Nov 30, 2019 at 10:40 PM Chris Murphy <lists(a)colorremedies.com>
On Thu, Nov 28, 2019 at 5:30 AM Kamil Paral <kparal(a)redhat.com>
> This is very similar to the Bugzilla description. For each proposed
blocker, we (auto-)create a ticket in a "fedora-blockers" project, for the
purpose of a blocker discussion. We interlink the bug and the ticket.
What about kanban? Is there kanban integration in pagure?
Or what about a taiga method, e.g. using teams.fedoraproject.org?
I'm not familiar with kanban/taiga. What is the benefit over using standard
I'm not opposed to dropping the live IRC blocker review entirely; but
even if it were true that they're cut down to a max 1 hour, or even an
informal day long working session on #fedora-qa, that would still be a
huge win. Probably a small subset of complex blocker bugs may benefit
from a live IRC meeting.
It should not be that hard to ping people participating in a particular
blocker ticket, and discuss some complex details over IRC, then write some
summary/findings to the ticket. That's a completely valid approach. Or
would you like to see something more formalized? What would the process