On Mon, Dec 2, 2019 at 11:47 PM Geoffrey Marr <gmarr@xxxxxxxxxx> wrote:
Kamil,Thanks for working on this. I am glad we are considering something different here, as the current process is not perfect.Personally, of the suggested options, I think that using Pagure is my preferred option. I think of the available options, it allows for the easiest collaboration between folks who are contemplating and voting on the bugs.However, I do resonate with some of what Ben said, specifically regarding losing the "live" setting when we vote. The ability to hash things out over IRC real-time is pretty valuable, and to use a different system where time between comments could become large, I wonder if still having a meeting every Monday would be advantageous. Something to go over the votes that have been made on the Pagure page (or whatever system it ends up being). The problem with that is keeping it from turning right back into the old "blocker-review-meeting". We could possibly institute a 30(?) minute time limit, where we go over the bugs to ensure we understand them and then accept the vote right there. That way we have the opportunity to ask questions/clarifications that might be tedious and take a lot of time over a forum-style messaging app. Again, there would have to be some kind of watchdog to prevent us from turning these meetings into what we have now. All this said, should this IRC meeting idea come to fruition, I would be more than happy to coordinate and run these, should anyone else not want to (adamw! :P)
I wonder if we could merge the live+async approaches to get the best of both. What if we handled simple/standard issues fully in tickets, and for complex issues which are difficult to understand and debug, or which have some heated discussions, we'd schedule an IRC meeting and resolve them there? We can either schedule the meetings ad-hoc, or we can use a special tag in Pagure, and the regular Monday blocker review meeting would only occur if there was at least a single open ticket marked with this tag. Does that sound better in your opinion?
_______________________________________________ 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