Sounds to me like it'd just be more work because someone would have to go around reviewing the tasks it closes and probably reopening the majority.
Also it doesn't make much sense to do this at a project-level, if it's done it should probably be across the whole of Wikimedia Phabricator.
Just because there hasn't been anyone to work on the task doesn't mean it's now irrelevant.

On Wed, 12 Dec 2018 at 09:19, Giovanni Tirloni <gtirloni@wikimedia.org> wrote:
Hello,

  Like any large project, we have a lot of old tasks/tickets/issues
opened and it's hard to know what is still relevant, considering that a
lot has changed, or there hasn't been anyone to work on them, etc.

  To keep things under control, some open source projects have adopted a
time limit on how long these can stay open. I would like to propose we
do the same.

  A soft threshold would trigger a warning being added to the task
saying it's going stale. After a hard threshold is reached, the task
would be closed.

  This doesn't mean someone can't re-open the task and we could also
have a special tag preventing the stale mechanism to activate on it.

  Any thoughts?

Thank you

--
Giovanni Tirloni
Operations Engineer
Wikimedia Cloud Services

_______________________________________________
Cloud-admin mailing list
Cloud-admin@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/cloud-admin