AUR orphan request automation
💡
Idea proposal Checks
NOTE: The below check boxes must be checked before the accompanying idea will be considered.
-
I have checked that the idea is not directly tied to a specific project For example: "Show label icons in the package overview web page" must be a feature request in the ArchWeb repository -
I have carefully checked this idea is not already covered by any open or closed ideas. -
I understand that I hold no copyright claims and that this idea can be adapted and used by Arch Linux in any arbitrary shape or form.
Summary
One of the duties assigned to Trusted Users is the handling of AUR reports that come in. The majority of these are orphan requests due to inactive maintainers. We have to wait 14 days before accepting such a request, and they're often left behind because of this. I'm proposing some sort of automated system by which orphan requests get accepted after the waiting period if the current maintainer does not contest it.
Motivation
There are over 250 open requests on the AUR as of right now. Going through the deletion and merge requests is fairly easy as they can be accepted or closed right away, while orphan requests tend to be forgotten and left to rot. The main way for AUR maintainers to state they're "still active" is with an email reply to the auto-generated ticket for the request... but going back and checking the mail archives to find those is too cumbersome.
Specification
This would require aurweb changes to accept the requests automatically as well as give the current maintainers a way to close them. (Since this involves a policy change in addition to aurweb changes, I think it's still fine to be listed here.)
One edge case to consider would be if the AUR maintainer claims to be active (by closing the request) but continues to let the package linger at an older version. In those situations, a TU could still step in to resolve it manually.