Case Study for removal automation of PRs submitted by accounts deleted by Github / "Ghosts"

[dnsguru]

The volunteers often get their time completely wasted by 'spaghetti at wall to see what sticks' experimental projects related to containers, anycast, dynamic-dns or other spin-up entrepreneurial or community projects that spin up and then crater or have the github accounts ghosted/deleted, leaving cleanup debris for the volunteer/maintainers to deal with. It's expensive but considered free.

Here is an example project, so that one can see the play and all its acts:

The creation PRs for neko.am and voxel.sh: https://github.com/publicsuffix/list/pull/953 https://github.com/publicsuffix/list/pull/1014

[somewhere along the line the project evaporates]

Revision PRs / removal recommendations from: https://github.com/publicsuffix/list/pull/1656 https://github.com/publicsuffix/list/pull/1753 https://github.com/publicsuffix/list/pull/1741

Irritated subsequent registrants (likely more): https://github.com/publicsuffix/list/pull/1840

These stack up and take a substantial amount of time, which expands with each subsequent request, and create very complicated review processes that take a lot of care in review so as to not delete entries unintentionally in 'friendly fire' situations.

[dnsguru]

in this particular issue, in looking at all the layers of the complexity, the course forward I propose is to layer the processing of #1741 and #1755 together, which effectively addresses #1840 and deals with part of #1753

[simon-friedberger]

I think the last activity here was #1996 and otherwise there is nothing to do except maybe introduce automation for deletions at some point.