On Sun, Aug 7, 2022 at 12:31 PM Kevin Fenzi <ke...@scrye.com> wrote: > On Sat, Aug 06, 2022 at 10:05:40PM +0200, Maxwell G via epel-devel wrote: > > We could create an issue tracker for this. Packagers would have to > > submit a ticket requesting to orphan a certain package's EPEL branch(es) > > and set the EPEL Bugzilla assignee to "orphan" if they're orphaning all > > active EPEL branches. epel-devel@ could be CC'd on all issues. Then, we > > could have a provenpackager in the SIG go through and manually retire > > the packages that haven't been picked up after six weeks. The later will > > be difficult if we have a large volume, but I don't expect that. We > > could script this if necessary or just ask the submitter to do it > > themself. > > > > This doesn't allow picking up packages in a self-service manner, but I > > don't think that's a huge deal for our case. >
After some discussion in our weekly EPEL Steering Committee meeting Maxwell's idea seems to lead the way. Maxwell has setup of pagure repo, to track these orphan issues. A pagure repo gives us the opportunity to have a nice README that people can see if they are unsure of the process. A pagure issue also seems more user friendly than a bugzilla. Both for the person creating the issue, and for others tracking it. https://pagure.io/epel/package-orphan-requests The policy isn't setup yet, but we are moving in the right direction. Troy
_______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@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/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
