Page MenuHomePhabricator

FlaggedRev installation requests (tracking)
Open, LowestPublic

Description

Creating tracking bug for ease of further future changes

Details

Reference
bz29744

Related Objects

StatusAssignedTask
OpenNone
ResolvedRobH
ResolvedReedy
ResolvedReedy
ResolvedReedy
InvalidNone
ResolvedReedy
DeclinedNone
ResolvedReedy
ResolvedReedy
InvalidNone
ResolvedReedy
ResolvedDereckson
ResolvedKrenair
ResolvedDereckson
DeclinedNone
ResolvedPiRSquared17
InvalidArystanbek
InvalidNone
ResolvedMdann52
InvalidNone
InvalidNone
InvalidNone
InvalidNone
InvalidNone
StalledNone
StalledNone
StalledNone
StalledRazeSoldier

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 11:31 PM
bzimport set Reference to bz29744.
bzimport added a subscriber: Unknown Object (MLST).
Reedy created this task.Jul 6 2011, 7:58 PM

Is there any idea when or if this will gonna be solved?

After talking this through with colleagues, our answer is that we are not accepting new wikis to enable Flagged Revisions, given the very significant problems that Flagged Revisions poses in terms of engaging new users, adding complexity and confusion to the existing too-hard-to-understand interface, and badly impacting the quantity, quality and depth of the wikis on which it has been used.

Sorry for the slowness of the response.

revi added a subscriber: revi.Dec 4 2014, 9:21 AM
jeblad added a comment.EditedMay 7 2015, 8:03 AM

I am going to rise this question again in the community, as I don't think WMF should impose such limits on the individual communities. Either we should have a lot better explanation or Jdforrester-WMFs blocking of this must be overruled by WMF itself.

Dereckson added a comment.EditedMay 11 2015, 10:13 AM

I am going to rise this question again in the community, as I don't think WMF should impose such limits on the individual communities. Either we should have a lot better explanation or Jdforrester-WMFs blocking of this must be overruled by WMF itself.

Hmmm... there is the main issue of who is willing to configure Flagged Revisions.

On philosophical grounds, as a volunteer, I'm not really inclined to handle such requests. @Reedy in your bug explicitly says the configuration process is painful.

So, to process Flagged Revisions requests, we need a volunteer who:

  1. doesn't have any conscientious objection
  2. knows how Flagged Revisions work
  3. has two to six hours of time to contribute to the initial configuration, then also blocks of one to two hours to see how things evolve, and if tweaking is needed, as a weeks/months commitment.

Or we can assign these tasks to a WMF employee, with the same heavy time and commitment constraint.

Glaisher lowered the priority of this task from Medium to Lowest.May 11 2015, 12:27 PM
Glaisher added a subscriber: Glaisher.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptNov 28 2015, 4:13 PM
Danny_B added a subscriber: Danny_B.
Danny_B removed a subscriber: Danny_B.

To get feedback from the global community on the FlaggedRevs deployment opportunity, I've launched a RfC on meta.

FDMS added a subscriber: FDMS.May 12 2016, 10:19 PM
MarcoAurelio changed the task status from Open to Stalled.Mar 18 2017, 1:12 PM
MarcoAurelio changed the task status from Stalled to Open.Mar 18 2017, 1:13 PM

I believe this must have a solution, and the present situation can't continue.

Reedy changed the status of subtask T194389: Enable $wgUseRCPatrol on azwiki from Open to Stalled.May 10 2018, 12:34 PM
Neriman2003 added a subscriber: Neriman2003.EditedMay 10 2018, 12:58 PM

We have translated the system messages.
(this is a consensus) Please install FlaggedRevs extension on azwiki.

@Neriman2003: This task T31744 is a general task. Please discuss azwiki-only stuff in its existing dedicated task T194389. It is off-topic here. Thanks.

FDMS removed a subscriber: FDMS.Sep 14 2018, 6:33 PM