Last modified: 2014-02-12 23:39:52 UTC
As part of the AdminTools project, it was identified that allowing centralized AbuseFilter rules would significantly reduce the workload for stewards. Code for this was put into AbuseFilter in Id69a9d603f9679f838e8691c651a3e9d8461b422, and is enabled on an individual wiki with a config option. Only users with the abusefilter-modify-global permission can create filters that will be applied globally. In order to deploy this we will: * Configure a small set of wikis (test, test2, and mediawiki.org) to use rules from meta, to verify that there is no significant performance impact. * Give Stewards the abusefilter-modify-global * Deploy to further wikis
The first step, enabling the configuration on test, test2, and mw.org has been completed: https://gerrit.wikimedia.org/r/#/c/48070/ If no issues are identified, we'll enable to permission in the next few days, and and continue to monitor performance while Stewards write rules for these enabled wikis.
Pending the merging of https://gerrit.wikimedia.org/r/#/c/42800/, stewards probably aren't going to do anything with it, except perhaps very limited testing.
(In reply to comment #2) > Pending the merging of https://gerrit.wikimedia.org/r/#/c/42800/, stewards > probably aren't going to do anything with it, except perhaps very limited > testing. I came to think that this is the wrong approach and would rather see this fixed within the AbuseFilter extension itself, possibly even allowing local admins to disable global filters.
(In reply to comment #1) > If no issues are identified, we'll enable to permission in the next few days, > and and continue to monitor performance while Stewards write rules for these > enabled wikis. I'm a bit confused as to the status of this bug.
I think Jasper is saying bug 43761 should be a blocker for this? If that's the intent, please add it as a blocker. Hoo, let's keep the discussion about local disabling there.
