epel

#205 Create an "orphaning" process
Closed: Cant Fix by carlwgeorge. Opened by tdawson.

Closed: Cant Fix
Reopen Issue

Fedora has a nice orphaning process. If a package maintainer decided they don't want to maintain a Fedora package anymore, they mark the package "Orphan" and give a reason. The package then goes through an automated process where emails go out, and others can take the orphaned package. After some time, if nobody has taken the package, the package is retired.

It would be nice to have something similar for EPEL packages.

Long ago, we had a concept of per-branch "ownership" with pkgdb. We lost that in the move to dist-git on pagure. Eventually we gained the collaborator permission, but it's not really the same. As it stands, packages are orphaned at the repo level, not the branch level.

Planning is underway for dist-git on forgejo. I suggest filing an issue with the Fedora Forge team to see if per-branch orphaning is something that can be considered.

https://forge.fedoraproject.org/forge/forge/issues

Metadata Update from @carlwgeorge:
- Issue close_status updated to: Cant Fix
- Issue status updated to: Closed (was: Open)

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/epel/steering/issues/205

Please continue any further discussion there.
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.