[Feature] Decouple disown and orphan logic
-
I have summed up the feature in concise words in the Summary section. -
I have completely described the feature in the Description section.
Summary
The /disown
action route currently deals with both non-request-based disowning and request-based orphaning of a package depending on the user's account type.
Description
We should decouple /disown
away from request-based orphaning. This aligns more with the UNIX philosophy of "one component does one thing" and makes these routes more easily understood by users.
I propose a /pkgbase/{name}/orphan
route, which is pretty much a verbatim copy of current /pkgbase/{name}/disown
. We could then treat disownage independently from absolute orphaning.
With that, we could then add an Orphan Package
action link to the requests section of the side-panel and move Adopt/Disown up on top of Manage Co-Maintainers
.