On "gardening" code reviews

[Luigi Toscano]

Hi,

I see the the gardening started also on stale reviews.
I think it should be opt-in, only for projects which request it.
If that's the case already, please skip the rest (or read it anyway, it may be
relevant if the policy changed).

We have projects which are, let's say, sleepy, were reviews are not taken into
account. You may say that, if some project is stale, it should go along its
fate and be archive.
I don't fully agree with that. As the KDE developer status allows access to
each and every repository, a project may get some renewed interest at some
point, and we have had several examples of this in the past.

Now, I believe that automatically closing code contributions (which are
slightly different beasts than bugs) can accelarate the process of making a
project look obsolete, rather than helping them to be back. Having the reviews
around may be a way for new contributors as start with a certain projects (by
rechecking them and merging). It's true that the reviews are still there, just
closed, but it's not the same in terms of visibility.

Ciao
-- 
Luigi