I believe that I've seen discussions of RC patrolling on ENWP too, although
I can't recall specifics. I am not familiar with the original discussion,
although my first guess is that the experienced patrollers were surprised
and that the surprise factored into their opposition to the change.
This is one of things Scoring platform team wanted to tackle because having
RC patrolling enabled for a wiki + ORES predications can improve efficiency
of the patrollers significantly but we didn't have community relations
resources to start the discussion with communities and get it approved.
On Sat, 9 Mar 2019 at 11:50, bawolff wrote:
> In regards to wgUseRCPatrol - I suspect (but don't know) that originally
> that was disabled on enwiki as a performance thing. If it was a performance
> concern, that's probably irrelevant at this point.
>
Sadly, no. It was enabled as a new feature
On 2019-03-09 16:12, Eran Rosenthal wrote:
- wmgUseSandboxLink
- Enabled in 80 wikis. Why not enabling it everywhere?
It was enabled on all wikis that were already adding a link to a user's
personal sandbox using site JS or a gadget enabled by default.
I wrote that extension as
In regards to wgUseRCPatrol - I suspect (but don't know) that originally
that was disabled on enwiki as a performance thing. If it was a performance
concern, that's probably irrelevant at this point.
I generally agree that its good to try an unify config complexity where it
makes sense. But I
I suspect that a major factor in whether or not to deploy many of these
extensions to every wiki is that, frankly...not every wiki has enough
active editors for these extensions to make sense or to be helpful. In
some ways, the extension may well be unhelpful or could act to distract the
few
Hi,
Wiki communities can ask to override their default configurations
(following consensus). The reasons to override may vary:
1. *customization* for community to align to community specific policy
(example: special namespaces / upload policy/user groups rights defined per
project and
