Jesse Keating wrote:
Instead of creating a bunch of different ways to "timeout" a maintainer and "do something" after the fact, why can't we just fix up the non-responsive policy? I'd rather have one policy than n+ for each situation.
This is meant to be a addition/modification of the non responsive maintainer's policy as noted in
https://www.redhat.com/archives/fedora-devel-list/2008-July/msg00744.html Rahul -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
