quality/tickets
9
3
Fork 0
Code Issues 46 Projects Activity Actions

Find new maintainers for Packager Dashboard + Oraculum #860

New issue
Closed
opened 2026-01-19 14:50:59 +00:00 by kparal · 7 comments
kparal commented 2026-01-19 14:50:59 +00:00
Owner
Copy link

Last year we decided to orphan Packager Dashboard and its backend Oraculum, because we don't have the manpower to maintain it and it's not closely related to Quality tasks. In the document we wrote:

This is well-loved by many Fedora packagers and we know it. It would be a pity to lose it. We might be able to find new maintainers within Red Hat. If that doesn’t work out, we’ll send an announcement asking for community maintenance.

The purpose of this ticket is to find the new maintainers.

The projects are currently on Pagure here:
https://pagure.io/fedora-qa/packager_dashboard
https://pagure.io/fedora-qa/oraculum

Last year we [decided](https://discussion.fedoraproject.org/t/fedora-quality-scope-reduction-announcement-and-summary/160523) to orphan [Packager Dashboard](https://packager-dashboard.fedoraproject.org/) and its backend Oraculum, because we don't have the manpower to maintain it and it's not closely related to Quality tasks. In the document we wrote: > This is well-loved by many Fedora packagers and we know it. It would be a pity to lose it. We might be able to find new maintainers within Red Hat. If that doesn’t work out, we’ll send an announcement asking for community maintenance. The purpose of this ticket is to find the new maintainers. The projects are currently on Pagure here: https://pagure.io/fedora-qa/packager_dashboard https://pagure.io/fedora-qa/oraculum
kparal commented 2026-01-19 14:54:41 +00:00
Author
Owner
Copy link

Metadata Update from @kparal:

  • Custom field story_points adjusted to 3
  • Issue set to the milestone: Undefined Future
**Metadata Update from @kparal**: - Custom field story_points adjusted to 3 - Issue set to the milestone: Undefined Future
kparal changed title from Find new mantainers for Packager Dashboard + Oraculum to Find new maintainers for Packager Dashboard + Oraculum 2026-02-05 14:23:55 +00:00
kparal commented 2026-05-27 19:57:46 +00:00
Author
Owner
Copy link

This has suddenly increased in priority, because we (well, Kevin) realized it's still hosted on Pagure, and we're not sure whether we can migrate it off Pagure once it gets decommissioned (around June 14-16, 2026). So we either need to find a new maintainer NOW, or we need to migrate it to our Quality Forge, and then move it/migrate it again to the new owner. But it would certainly be better to do just a single migration.

Let's ask CLE first, and if they don't want it, make a public call.

This has suddenly increased in priority, because we (well, Kevin) realized it's still hosted on Pagure, and we're not sure whether we can migrate it off Pagure once it gets decommissioned (around June 14-16, 2026). So we either need to find a new maintainer NOW, or we need to migrate it to our Quality Forge, and then move it/migrate it again to the new owner. But it would certainly be better to do just a single migration. Let's ask CLE first, and if they don't want it, make a public call.
kparal self-assigned this 2026-05-27 19:58:08 +00:00
kparal added this to the Sprint 11 project 2026-05-29 15:17:37 +00:00
kparal removed this from the Undefined Future milestone 2026-05-29 15:17:43 +00:00
kparal commented 2026-06-01 16:08:59 +00:00
Author
Owner
Copy link

The projects were migrated off Pagure into the apps org:
https://forge.fedoraproject.org/apps/packager_dashboard
https://forge.fedoraproject.org/apps/oraculum

That doesn't mean CLE want to maintain them, but we have more time to find the new owners. I'll submit a mailing list call to the devel list next.

The projects were migrated off Pagure into the apps org: https://forge.fedoraproject.org/apps/packager_dashboard https://forge.fedoraproject.org/apps/oraculum That doesn't mean CLE want to maintain them, but we have more time to find the new owners. I'll submit a mailing list call to the devel list next.
kparal commented 2026-06-10 09:53:06 +00:00
Author
Owner
Copy link

Devel list call for maintainers: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/RVCAUQE6N4R3P3C6FSBOKGDZG6CND6ZR/

Devel list call for maintainers: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/RVCAUQE6N4R3P3C6FSBOKGDZG6CND6ZR/
kparal commented 2026-06-12 07:45:54 +00:00
Author
Owner
Copy link

In the devel list thread, @frantisekz says the timeline uses https://pagure.io/package-calendars/ , so I created https://pagure.io/package-calendars/issue/6 to ask for migration.

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).

In the same thread, Tomi Lähteenmäki volunteered to help with maintenance. I'll wait some more for more feedback.

In the devel list thread, @frantisekz says the timeline uses https://pagure.io/package-calendars/ , so I created https://pagure.io/package-calendars/issue/6 to ask for migration. 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). In the same thread, Tomi Lähteenmäki volunteered to help with maintenance. I'll wait some more for more feedback.
kparal commented 2026-06-15 09:08:47 +00:00
Author
Owner
Copy link

For the purpose of sprint planning, this is now done.

I'll keep this ticket open to complete the handover to new maintainers (if there are some, but some applied already on the devel list), and/or communicate with Infra and decide the fate of the project.

For the purpose of sprint planning, this is now done. I'll keep this ticket open to complete the handover to new maintainers (if there are some, but some applied already on the devel list), and/or communicate with Infra and decide the fate of the project.
kparal commented 2026-06-23 11:06:07 +00:00
Author
Owner
Copy link

I've sent a direct email to Sheikh and Tomi with some additional info. Fedora infra already reviewed one PR, and they intend to do so until they can trust them enough to give them better access rights. I believe we've done everything we could from our side. Now it's up to the new maintainers.

I've sent a direct email to Sheikh and Tomi with some additional info. Fedora infra already reviewed one PR, and they intend to do so until they can trust them enough to give them better access rights. I believe we've done everything we could from our side. Now it's up to the new maintainers.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels   
agile
related to Scrum or other Agile methodology

  
anacondawebui
tickets relating to the anaconda 'web ui' interface refresh

  
arm

   
blockerfe
Issues relating to the blocker / freeze exception process

  
Closed As
Duplicate
 Closed with the reason of Duplicate

  
Closed As
Fixed
 Closed with the reason of Fixed

  
Closed As
Invalid
 Closed with the reason of Invalid

  
Closed As
Wontfix
 Closed with the reason of Wontfix

  
Closed As
Worksforme
 Closed with the reason of Worksforme

  
coreos
issue related to coreos

  
criteria
release criteria-related issues

  
defect

   
easyfix

   
enhancement

   
iot
Issues related to IoT

  
meeting
a topic for the next QA meeting

  
meta
issues in the issue tracker itself (like, whooooaaa, man)

  
onboarding call
issues that are used to track new contributor onboarding

  
proventesters

   
retrospective
issues filed as a result of QA Retrospective feedback

  
silverblue
Issues related to silverblue

  
sponsor
requests to become a FAS group sponsor

  
test cases

   
test days

   
wiki
  
ai-review-please
Request AI review for a pull request

  
Backlog Status
Needs Review
 Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
 Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

  
chore
Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  
documentation
Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  
points
01
 A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
 This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
 Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
 A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
 Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
 Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

  
Priority
Critical
 This is for work that is urgent and of critical importance and so and must be addressed immediately with a higher priority than all other work, even if not originally planned for the current sprint.

  
Priority
High
 This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
 This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
 This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
 Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
Sprint Status
Done
 Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
 Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
 Work items that are complete but need review, testing, or approval before being marked as done.

  
Sprint Status
To Do
 Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt
Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

  
Work Item
Bug
 Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic
 Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Work Item
Spike
 Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
 Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  
Work Item
User Story
 User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels
agile
anacondawebui
arm
blockerfe
Closed As
Duplicate
Closed As
Fixed
Closed As
Invalid
Closed As
Wontfix
Closed As
Worksforme
coreos
criteria
defect
easyfix
enhancement
iot
meeting
meta
onboarding call
proventesters
retrospective
silverblue
sponsor
test cases
test days
wiki
ai-review-please
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Sprint 11
Assignees
Clear assignees
No assignees
kparal
adamwill
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
quality/tickets#860
No description provided.