I looked at the issues and added my own evaluation of these tickets.
I would probably recommend to use numbers corresponding to
low(1)-medium(2)-high(3) value and use some excel like document to have
average value in some summary row.
Something like the structure bellow (I will use the CSV format delimited
by ;):
Issue #;Name;Url;Trouble;Gain;Note;
And this filled with my own prioritization:
8455;Move mailman to newer release of Fedora or
CentOS;https://pagure.io/fedora-infrastructure/issue/8455;3;2;I see that
the mailman needs multiple changes to be moved to RHEL 8. It will be
nice to have that, but the gain is not that high.;
Just my 2c. This will make most of the work with data automatic and you
could even use the document as input for some tagger script, that will
tag the tickets.
Regards,
Michal
On 09/03/2020 14:47, Clement Verna 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 I see that the mailman needs
multiple changes to be moved to RHEL 8. It
will be nice to have that, but the gain is not that high.
Trouble : high
Gain : medium
#8167 Adding topic authorization to our RabbitMQ instances -
https://pagure.io/fedora-infrastructure/issue/8167 This sounds like most of the
work is done, so I say low trouble. It will
solve possible security issue, so I will go with medium-gain.
Trouble : low
Gain : medium
#8035 A few final ansible secrets for kerneltest -
https://pagure.io/fedora-infrastructure/issue/8035 I think this shouldn't be
that much trouble to add a few other
variables. Not sure how much gain we get for this, so I will go with low.
Trouble : low
Gain : low
#7935 Nightlies (Rawhide and Branched) not imported to PDC -
https://pagure.io/fedora-infrastructure/issue/7935 This is too much trouble for low
gain, we should direct our manpower to
FPDC instead.
Trouble : high
Gain : low
#7919 Fix fas fedmsg sending in openshift -
https://pagure.io/fedora-infrastructure/issue/7919 We will replace FAS soon and
fedmsg should be replaced by
fedora-messaging. So low gain and high-trouble.
Trouble : high
Gain : low
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 -- infrastructure(a)lists.fedoraproject.org
To unsubscribe send an email to infrastructure-leave(a)lists.fedoraproject.org
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/infrastructure@lists.fedora...
--
Role: Fedora CPE Team - Software Engineer
IRC: mkonecny
FAS: zlopez