Hello, a year ago I announced https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/E4TT2PEOSITJ4PJP44L2GQUU4CA6R6B3/#ZJGYOMU6I7LEETQ4YEH6ZJBSC5VEM653 and launched the Fedora Review Service https://github.com/FrostyX/fedora-review-service. Nobody complained that it is annoying, and I am getting pings from people when there is an outage, so I consider this endeavor to be a success :-)
Since its last release, the service parses and shows recommendations based on the fedora-review.json https://github.com/FrostyX/fedora-review-service/pull/33 output. There is a nice secondary use of this feature - we can do something when no errors are found. My plan is to set the `AutomationTriaged` Bugzilla keyword for such tickets. Or any other keyword that you would prefer. As a follow-up, I want to unleash the service on all open review tickets, so that even tickets that predate the service can obtain the `AutomationTriaged` keyword.
RFE https://github.com/FrostyX/fedora-review-service/issues/13
The endgame will be adding "CI passing tickets" section to the Cached Package Review Tracker https://fedoraproject.org/PackageReviewStatus/ and/or adding some special row color for tickets that passed the automated review to already existing sections https://fedoraproject.org/PackageReviewStatus/reviewable.html.
My motivation for this feature is to make life easier for reviewers. They will be able to focus on tickets that passed an automated review and therefore are more likely to be in an (almost) acceptable state.
What do you think? Jakub
On Saturday, 09 December 2023 at 19:32, Jakub Kadlcik wrote:
Hello, a year ago I announced https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/E4TT2PEOSITJ4PJP44L2GQUU4CA6R6B3/#ZJGYOMU6I7LEETQ4YEH6ZJBSC5VEM653 and launched the Fedora Review Service https://github.com/FrostyX/fedora-review-service. Nobody complained that it is annoying, and I am getting pings from people when there is an outage, so I consider this endeavor to be a success :-)
Yes, it is very useful. I like it a lot.
Since its last release, the service parses and shows recommendations based on the fedora-review.json https://github.com/FrostyX/fedora-review-service/pull/33 output. There is a nice secondary use of this feature - we can do something when no errors are found. My plan is to set the `AutomationTriaged` Bugzilla keyword for such tickets. Or any other keyword that you would prefer. As a follow-up, I want to unleash the service on all open review tickets, so that even tickets that predate the service can obtain the `AutomationTriaged` keyword.
RFE https://github.com/FrostyX/fedora-review-service/issues/13
Cool! Go for it.
The endgame will be adding "CI passing tickets" section to the Cached Package Review Tracker https://fedoraproject.org/PackageReviewStatus/ and/or adding some special row color for tickets that passed the automated review to already existing sections https://fedoraproject.org/PackageReviewStatus/reviewable.html.
Great idea.
My motivation for this feature is to make life easier for reviewers. They will be able to focus on tickets that passed an automated review and therefore are more likely to be in an (almost) acceptable state.
What do you think?
This is excellent work. Thank you so much for doing this.
Regards, Dominik
Thank you for the feedback Dominik,
Cool! Go for it. Great idea.
I am going for it then :-)
On Sat, Dec 9, 2023 at 10:20 PM Dominik 'Rathann' Mierzejewski < dominik@greysector.net> wrote:
On Saturday, 09 December 2023 at 19:32, Jakub Kadlcik wrote:
Hello, a year ago I announced <
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/...
and launched the Fedora Review Service https://github.com/FrostyX/fedora-review-service. Nobody complained that it is annoying, and I am getting pings from people when there is an outage, so I consider this endeavor to be a success :-)
Yes, it is very useful. I like it a lot.
Since its last release, the service parses and shows recommendations
based
on the fedora-review.json https://github.com/FrostyX/fedora-review-service/pull/33 output.
There is
a nice secondary use of this feature - we can do something when no errors are found. My plan is to set the `AutomationTriaged` Bugzilla keyword for such tickets. Or any other keyword that you would prefer. As a
follow-up, I
want to unleash the service on all open review tickets, so that even tickets that predate the service can obtain the `AutomationTriaged`
keyword.
RFE https://github.com/FrostyX/fedora-review-service/issues/13
Cool! Go for it.
The endgame will be adding "CI passing tickets" section to the Cached Package Review Tracker https://fedoraproject.org/PackageReviewStatus/
and/or
adding some special row color for tickets that passed the automated
review
to already existing sections https://fedoraproject.org/PackageReviewStatus/reviewable.html.
Great idea.
My motivation for this feature is to make life easier for reviewers. They will be able to focus on tickets that passed an automated review and therefore are more likely to be in an (almost) acceptable state.
What do you think?
This is excellent work. Thank you so much for doing this.
Regards, Dominik -- Fedora https://fedoraproject.org There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Many thanks Jakub. It is a helpful tool. Hopefully it will also encourage more community contributions to help improve and update Fedora Review as well.