auto-close "rotten" issues per fejta-bot k8s example

[jctanner]

https://github.com/kubernetes/minikube/issues/2527#issuecomment-404647040

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close
--

We should consider as a point of project governance that inactive issues aren't being worked.

[gundalow]

Interesting workflow. This seems to be closing any any issue older than 90 (or 120 days).

If anyone is working on a fix for the issue do we want to require/enforce:

• they are assigned
• a comment along the lines of "I'm working on this"?

@jctanner how did you imagine the workflow looking like?

[webknjaz]

Ref: https://github.com/ansible/ansible/pull/58674 / https://github.com/dessant/lock-threads/issues/14

[webknjaz]

they are assigned

FTR modern GitHub allows assigning issues to any users who commented them ever.

[dessant]

@webknjaz, I think Stale is a better fit for this use case, Lock Threads operates on issues that were already closed.

[webknjaz]

@dessant that's a different case but related. Originally I wanted to replace what @sivel's been doing manually.

[geerlingguy]

We discussed this at AnsibleFest Atlanta during the Community Summit. The in-room consensus was to use a model similar to K8s' bot, where:

• After 30d with no activity, open feature request is marked 'stale'
• After 90d with no activity, open feature request is closed

The bot would ideally also be able to interpret issue-related comments like close/notstale/etc. like https://github.com/kubernetes/test-infra/tree/master/prow#bots-home