Reinstate the automated mechanism for pinging/closing issues that are stuck in Needs More Info

During a discussion on the development mailing list, it emerged that some kind of automation was implemented in mid-2018 to ping issues that have been idle in the Needs More Info state for a while and to close those that appear to be permanently stranded there (i.e. previous pings have been ignored for too long).

It appears that this mechanism broke shortly after being implemented as there are now more than 900 open Needs More Info bugs, some dating back to the second half of 2018.

Please:

a) Reinstate this mechanism in a way that starts the clock again, i.e. ping every Needs More Info issue that's been stuck for more than one month and wait another month before closing any of them.

b) Provide a way for one or more humans to be notified if the mechanism breaks again. That could be as simple as emailing the output of the job to one or more appropriate people each time it runs to provide reassurance that the job is still being run.  I am willing to be the recipient if nobody else is interested in volunteering.