Thanks all for your inputs and comments, this was really useful .

I have tagged these issues based on the feedback received, you can see all
the issues with at least one of these tags using this link [0]

[0] -
https://pagure.io/fedora-infrastructure/issues?status=Open&tags=high-trouble&tags=low-gain&tags=high-gain&tags=medium-gain&tags=medium-trouble&tags=low-trouble&priority=0&close_status=

On Mon, 9 Mar 2020 at 14:47, Clement Verna <[email protected]> wrote:

> Hi all,
>
> This is the first email with trying to better prioritize our backlog of
> ticket ( https://pagure.io/fedora-infrastructure/issues ).
>
> So let's look at 5 tickets and rate them using the following categories :
> * low-trouble, medium-trouble, high-trouble
> * low-gain, medium-gain, high-gain
>
> #8455 Move mailman to newer release of Fedora or CentOS -
> https://pagure.io/fedora-infrastructure/issue/8455
> Trouble : ?
> Gain : ?
>
> #8167 Adding topic authorization to our RabbitMQ instances -
> https://pagure.io/fedora-infrastructure/issue/8167
> Trouble : ?
> Gain : ?
>
> #8035 A few final ansible secrets for kerneltest -
> https://pagure.io/fedora-infrastructure/issue/8035
> Trouble : ?
> Gain : ?
>
> #7935 Nightlies (Rawhide and Branched) not imported to PDC -
> https://pagure.io/fedora-infrastructure/issue/7935
> Trouble : ?
> Gain : ?
>
> #7919 Fix fas fedmsg sending in openshift -
> https://pagure.io/fedora-infrastructure/issue/7919
> Trouble : ?
> Gain : ?
>
>
> Let's also use this thread to ask questions and clarifications if needed.
> Also if you have any ideas or feedback on how to improve that process I am
> happy to hear about it :-).
>
>
> Thanks
> Clément
>
_______________________________________________
infrastructure mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]

Reply via email to