Hello everyone (but especially package maintainers),
please note that Fedora Packager Dashboard currently has no maintainers, and the service breaks more and more over time. If the Packager Dashboard brings you value, please consider whether you can help maintain it. That doesn't necessarily mean development, just making sure it stays up and small occasional bitrot issues are fixed is a great help.
== What is the Packager Dashboard? ==
If you don't know Packager Dashboard, it shows lots of interesting information about the packages that you own in Fedora, e.g. Bugzilla tickets (with highlighted CVEs and FTBFS), Bodhi updates, distgit PRs, the current release schedule timeline, etc. Everything is structured per-package. You can access it at: https://packager-dashboard.fedoraproject.org/
Here's a short populated example for adamwill's dashboard: https://packager-dashboard.fedoraproject.org/dashboard?users=adamwill and here's much more complex and populated example for frantisekz's dashboard: https://packager-dashboard.fedoraproject.org/dashboard?users=frantisekz
You can modify the URL the see anyone's dashboard (please note that a first display for a particular user takes a longer time, because the values are not cached).
== Maintenance details ==
The Packager Dashboard is just a simple presentation UI, but most of the heavy-lifting is performed by Oraculum, that pulls data from different sources. So maintaining Packager Dashboard means maintaining both projects.
We've recently moved both projects from Pagure to Forge, under the Infra-maintained "apps" organization: https://forge.fedoraproject.org/apps/packager_dashboard https://forge.fedoraproject.org/apps/oraculum
That doesn't mean that Fedora Infra will maintain the apps, though. We see considerable value in the Packager Dashboard, that's why we moved it, but it still needs new maintainers. That's why I'm writing this email. We need to see if there are any volunteers willing to help, or if the service should be dropped. Furthermore, we're not even sure how many package maintainers know about this dashboard (because it's not promoted much), and how many consider it very useful and beneficial (or if it's just a minor help and people won't care if it goes away). Your feedback on these questions is also very welcome.
Thank you.
On ke, kesä 10 2026 at 11.51.35 +02:00:00, Kamil Paral kparal@redhat.com wrote:
Dashboard brings you value, please consider whether you can help maintain it. That doesn't necessarily mean development, just making sure it stays up and small occasional bitrot issues are fixed is a great help.
I might have limited time to help but sign me up, I'll try to help when I can.
-Tomi
On Wed, Jun 10, 2026 at 11:51:35AM +0200, Kamil Paral wrote:
Furthermore, we're not even sure how many package maintainers know about this dashboard (because it's not promoted much), and how many consider it very useful and beneficial (or if it's just a minor help and people won't care if it goes away). Your feedback on these questions is also very welcome.
I know about it and use it as the primary way to get an overview of bugs in smaller packages that I don't look at every week and to figure out what needs attention.
Zbyszek
On Thu, Jun 11, 2026 06:30:28 +0000, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Jun 10, 2026 at 11:51:35AM +0200, Kamil Paral wrote:
Furthermore, we're not even sure how many package maintainers know about this dashboard (because it's not promoted much), and how many consider it very useful and beneficial (or if it's just a minor help and people won't care if it goes away). Your feedback on these questions is also very welcome.
I know about it and use it as the primary way to get an overview of bugs in smaller packages that I don't look at every week and to figure out what needs attention.
+1, it's particularly useful to manage group packages. For example, the neuro-sig's dashboard is here:
https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig
Perhaps we can make it more visible? I can look at whether it's mentioned in the package maintainer docs etc.
I would like to see it remain alive, but I know nothing of the tech stack to be able to help with the maintenance :/
Hi,
(as one of the original dashboard's backend authors) I am hoping this will get at least some help and traction in the community, and at least some life-support and dependency refreshments here and there until some larger refactoring would most likely be needed once Fedora moves from bugzilla/pagure combo.
What I wanted to add here is that it also has one (maybe not "in the UI" well enough presented) feature is an option to create fully customized dashboards - either via an "account switch" icon, or directly at https://packager-dashboard.fedoraproject.org/custom , one can create a dashboard composed of different user packages, package groups, or explicit set of packages to be displayed. Such dashboard can then be shared between multiple people via a specific url containing all the set variables.
One last thing I'd mention would be support for custom schedules correlated to the packages displayed - their definitions are available at https://pagure.io/package-calendars (via plain files in that git repo) where users might add links to an ical files relevant to the packages for eg. upstream project schedules to be displayed.
Thanks, and crossing fingers!
On Thu, Jun 11, 2026 at 12:49 PM Ankur Sinha sanjay.ankur@gmail.com wrote:
On Thu, Jun 11, 2026 06:30:28 +0000, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Jun 10, 2026 at 11:51:35AM +0200, Kamil Paral wrote:
Furthermore, we're not even sure how many package maintainers know about this dashboard (because it's not promoted
much), and
how many consider it very useful and beneficial (or if it's just a
minor
help and people won't care if it goes away). Your feedback on these questions is also very welcome.
I know about it and use it as the primary way to get an overview of bugs in smaller packages that I don't look at every week and to figure out what needs attention.
+1, it's particularly useful to manage group packages. For example, the neuro-sig's dashboard is here:
https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig
Perhaps we can make it more visible? I can look at whether it's mentioned in the package maintainer docs etc.
I would like to see it remain alive, but I know nothing of the tech stack to be able to help with the maintenance :/
-- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London -- _______________________________________________ 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://forge.fedoraproject.org/infra/tickets/issues/new
On Thu, Jun 11, 2026 at 11:52 PM Frantisek Zatloukal fzatlouk@redhat.com wrote:
Hi,
(as one of the original dashboard's backend authors) I am hoping this will get at least some help and traction in the community, and at least some life-support and dependency refreshments here and there
Thanks for joining the discussion, Frantisek. Are you willing to help out new maintainers, if needed?
One last thing I'd mention would be support for custom schedules correlated to the packages displayed - their definitions are available at https://pagure.io/package-calendars (via plain files in that git repo) where users might add links to an ical files relevant to the packages for eg. upstream project schedules to be displayed.
I didn't know. I created a ticket for the project (CC @Miro Hrončok mhroncok@redhat.com ) to consider migrating it off Pagure: https://pagure.io/package-calendars/issue/6
Also, Frantisek ran some queries, and there were 151 unique dashboards displayed in the last 30 days. So clearly there are users (at least 151), but it would be great to promote it much more (if enough maintainers are found - thanks Tomi!).
On Fri, Jun 12, 2026 at 9:43 AM Kamil Paral kparal@redhat.com wrote:
On Thu, Jun 11, 2026 at 11:52 PM Frantisek Zatloukal fzatlouk@redhat.com wrote:
Hi,
(as one of the original dashboard's backend authors) I am hoping this will get at least some help and traction in the community, and at least some life-support and dependency refreshments here and there
Thanks for joining the discussion, Frantisek. Are you willing to help out new maintainers, if needed?
I'd gladly help out with PR reviews whenever time and workload in dayjob allows (that's not gonna be too often). Feel free to drop a ping if there is something in need of review or consultation :)
Hi,
I'm interested in helping with Packager Dashboard and would like to learn more about its current state.
What are the main challenges today, and what kind of maintenance work is typically needed?
Thanks, Sheikh Limon
On Mon, Jun 15, 2026 at 1:00 AM Sheikh Limon sheikhlimondev@gmail.com wrote:
What are the main challenges today, and what kind of maintenance work is typically needed?
First, a disclaimer: I've never maintained these projects, so I have no personal experience.
The current state is that PD+Oraculum were without a maintainer for about a year. And it was surprisingly stable, from what I know.
The initial maintenance would mostly involve the migration of the projects: https://forge.fedoraproject.org/apps/packager_dashboard/issues/191 https://forge.fedoraproject.org/apps/oraculum/issues/222 (That might be actually done by Fedora Infra instead).
Some of its dependencies got migrated as well, and will require code changes: https://forge.fedoraproject.org/apps/oraculum/issues/224
The containers which PD+Oraculum are using are outdated now and need replacing: https://forge.fedoraproject.org/apps/oraculum/issues/220 (But again Infra already did some work on this).
I guess it would also be good to update all libraries used in the project to the latest version.
After these changes are done, if you want to just maintain the app and not develop it further, I think there's nothing urgent. Just watch for things breaking (because of some API change, new library changing some behavior slightly, etc) and fix those.
There will be larger changes needed when big shifts in Fedora infra happen. E.g. Pagure is getting decommissioned soon, but it hopefully shouldn't affect Oraculum as long as it's still used for disgit (but it's good to check asap). But once distgit is moved, it will surely need updates for the new system. The same goes with Bugzilla, if/when we replace it, it will need updates for the new system.
I'm surely Frantisek can provide better instructions and tips, but he's away for a few weeks, he might reply here once he gets back.
Thanks, that helps a lot.
I started with https://forge.fedoraproject.org/apps/oraculum/issues/224 and opened PR https://forge.fedoraproject.org/apps/oraculum/pulls/225 with the calendars.py changes, API URL updates, a test stub, and a couple of stale URLs I noticed in conf/settings.py.example.
While setting up a development environment, I also ran into a few issues and opened tickets for them so they're tracked. Some are probably small fixes, others may need a bit more discussion.
I also have a few documentation fixes locally that I'll send separately once I clean them up.
For now I'm focusing on the smaller issues and cleanup tasks while I get familiar with the codebase.
On Fri, Jun 19, 2026 at 6:26 PM Sheikh Limon sheikhlimondev@gmail.com wrote:
I started with https://forge.fedoraproject.org/apps/oraculum/issues/224 and opened PR https://forge.fedoraproject.org/apps/oraculum/pulls/225 with the calendars.py changes, API URL updates, a test stub, and a couple of stale URLs I noticed in conf/settings.py.example.
While setting up a development environment, I also ran into a few issues and opened tickets for them so they're tracked. Some are probably small fixes, others may need a bit more discussion.
Awesome, thanks, Sheikh, for starting to work on this. I'll also ping Frantisek directly to ensure he's aware of this. (I'm afraid he no longer frequently visits Fedora mailing lists, Matrix, or the Forge. But it would be great if he could help you get familiar with the basics).
-
Ankur Sinha -
Frantisek Zatloukal -
Kamil Paral -
Sheikh Limon -
Tomi Lähteenmäki -
Zbigniew Jędrzejewski-Szmek