Page MenuHomePhabricator
Create Task
Maniphest T204354

Flagged Revisions for Vietnamese Wikipedia
Open, Stalled, LowestPublic
Actions

Description

Consensus: vi.wp

Hello, the Vietnamese Wikipedia community is requesting for enable Flagged Revisions on our local wiki. We are hoping a configure same as English Wikipedia, which only for targets page which get protected, but with both level of pending change and some particular setup only in Vietnamese Wikipedia. Here is details:

  • General rights:
1. Import ['reviewer'] and ['autoreview']

2. ['sysop'] and ['elminator'] default have the ['reviewer'] and ['autoreview'] rights

3. ['sysop'] can add/remove ['reviewer']

4. ['sysop'] can make protection for a page in both level pending changes
  • Rights custom per level pending changes

With pending change level 1:

['autoconfirmed'] default have ['autoreview'], their edits no need to be accepted by a ['reviewer'],  but if there are previous pending changes, no changes go live until the pending changes have been reviewed by a ['reviewer'],

With pending change level 2:

only ['sysop'] and ['elminator'] can accept or reject a revision

['reviewer'] can not accept or reject a revision

With this, we hoping to create two type of ['autoreview'] and ['reviewer'] group which match with their role in different pending change level. The Pening change level 1 is exactly same with the current configure for English Wikipedia (except we also have ['elminator'] group). And the Pening change level 2 maybe need a total new group so when a page is protecting by pending change level 2, only ['sysop'] and ['elminator'] can make page go to stable status, not normal ['reviewer'].

  • In the case pending change level 2 is impossible due technically issue and only one level pending change can be set-up
['sysop'], ['elminator'], ['reviewer'] can accept or reject a revision

no ['autoreview'] give for ['autoconfirmed'], their edits must be approve by user have ['reviewer'] rights as well.

This maybe complicated, and because we have new setting for pending change level 2, I can't create a configure page as what Portugal Wikipedia did. Sincerely apologize and hope someone can help me sort this out so developers can deploy it more easily. Also I guess a beta cluster wiki should be created so we can make sure the extension working properly follow which we are hoping as consensus above.

I will always online here to responde any question about this complicated configure, so please just feel free to ask anything can help you understand this request. Thank you!

Related Objects
Search...

StatusSubtypeAssignedTask
 OpenNoneT31744 FlaggedRev installation (deployment) requests (tracking)
 StalledNoneT204354 Flagged Revisions for Vietnamese Wikipedia
 OpenNoneT185664 Code stewardship review: FlaggedRevs
 OpenLadsgroupT277883 Drop all low-use and unused features of FlaggedRevs to make it more maintainable
 ResolvedLadsgroupT285608 Stop logging and clean up auto review logs
 DeclinedMarosteguiT288398 Drop two now-unused indexes on flaggedrevs table
 ResolvedLadsgroupT289248 Drop stable check for images used in pages
 ResolvedLadsgroupT289249 flaggedtemplates table should not keep the whole history of all revisions
 ResolvedMarosteguiT290057 Optimize flaggedtemplates tables in production
 ResolvedLadsgroupT300774 Drop fr_img_* columns
 ResolvedBUG REPORTNoneT302233 Toolforge db: View 'fiwiki_p.flaggedrevs' references invalid table/column/rights to use them
 ResolvedLadsgroupT301312 Switchover s1 master (db1118 -> db1163)
 ResolvedLadsgroupT300510 Upgrade s2 to Bullseye
 ResolvedMarosteguiT306417 Switchover s2 master (db1122 -> db1162)
 ResolvedMarosteguiT301850 Switchover s3 master (db1157 -> db1123)
 ResolvedMarosteguiT300473 Upgrade s5 to Bullseye
 ResolvedMarosteguiT303798 Switchover s5 master db1130 -> db1100
 ResolvedMarosteguiT300471 Switchover s6 master (db1173 -> db1131)
 DeclinedTrizek-WMFT302283 Read-only window needed for s6
 ResolvedLadsgroupT302363 Upgrade s7 to bullseye
 ResolvedMarosteguiT306001 Switchover s7 master (db1136 -> db1181)
 ResolvedZabeT262978 flaggedpage_config.fpc_select is unused
 ResolvedLadsgroupT306147 Make flaggedpage_config.fpc_select nullable on wmf wikis
 ResolvedLadsgroupT308933 Drop flaggedpage_config.fpc_select column on wmf wikis
 OpenLadsgroupT323495 flaggedrevs_statistics is holding millions of rows while FR needs only a handful

Event Timeline

minhhuy created this task.Sep 14 2018, 2:17 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSep 14 2018, 2:17 PM
minhhuy renamed this task from Enabler Flagged Revisions for Vietnamese Wikipedia to Flagged Revisions for Vietnamese Wikipedia.Sep 14 2018, 2:17 PM
Mainframe98 removed a project: Shell.Sep 14 2018, 2:20 PM
MarcoAurelio added a project: Wikimedia-Extension-setup.Sep 14 2018, 6:24 PM
MarcoAurelio moved this task from Backlog to Flagged Revisions on the Wikimedia-Extension-setup board.
MarcoAurelio added a parent task: T31744: FlaggedRev installation (deployment) requests (tracking).
MarcoAurelio changed the task status from Open to Stalled.Sep 14 2018, 6:28 PM
MarcoAurelio triaged this task as Lowest priority.
MarcoAurelio added subscribers: Dereckson, Nemo_bis, MarcoAurelio.

Stalling per T137937#2386610, which is still true at this moment; but translatewiki.net translation stats shows 99% of translated messages so that shouldn't be a blocker. Ping @Dereckson and @Nemo_bis just in case. Thanks.

MarcoAurelio moved this task from Backlog to Blocked on development on the Wikimedia-Site-requests board.Sep 14 2018, 6:29 PM
minhhuy added a comment.EditedSep 14 2018, 7:33 PM

I read the discussion about Flagged revisions on Meta to figure the future of extension as Dereckson said in ur.wp case, but the discussion ended and more community still waiting for deploy this tool in their wikis.

Also, Vietnamese Wikipedia not a "new wiki", we are having 1 millions article and active since 2003, with a Wikimedia user group get approved recent time. So we even not in the scope of the discussion on Meta, which target for small and new community.

And we sure have "significant planning" about deploy the tool in our wiki. The total discussion time to get consensus took about 3 month (15 days voting) with all documention and guideline pages (as 1, 2, 3) get prepared even 2 years ago before the discussion. We know what we should do once the extension come to our wiki. What we are preparing here is a model same as English Wikipedia which the "pening change level" only for few pages get protection by a sysop, not a full wiki so there will be no back log at all (because as in the rule, we only allow a page in pending change protection at a certain time, not eternal). Only different is we want a higher level of pending change, which also already setted up before in English Wikipedia, about only sysop can accept a revision in very minority and seriously case to prevent BLP and COI violation (in Vietnamese Wikipedia, we always in emergency case with the topic about political when it related to Vietnam government (similarity to China government), where NPOV invasion all the articles and no anyway to prevent systemic vandalism with sockpuppets, lasting for already more 5 years). We believe that in somecase, this tool help us raise the "open" spirit, instead a page get totally protection or semi-protection as normal, which almost useless in our wiki.

All what I said above already presented in our local consensed discussion and can be verify with machine translation, just for make sure what I am saying here is really in line with the current situation of Vietnamese Wikipedia and how we needing the Pending Change.

minhhuy updated the task description. (Show Details)Sep 15 2018, 6:46 AM
minhhuy added a comment.Oct 5 2018, 4:32 AM

Will this request have any chance to be process? The current development of Vietnamese Wikipedia really need support of reviewer as soon as possible.

Aklapper added a comment.Oct 5 2018, 10:27 AM

I'm afraid https://meta.wikimedia.org/wiki/Flagged_Revisions#Enabling still applies. :-/

minhhuy added a comment.EditedOct 5 2018, 2:40 PM

@Aklapper As I wrote above, the RfC already closed without any result about deploy or not this tool in future. In the case WMF decided to remove this tool or will not setup for new request, there should be a at least a notice about that decision.

Vietnamese Wikipedia is big wiki with an very actively community, we aware about the effect of PendingChanges, we are not "new small communities like to do extension and config shopping, to have all their wikis configured like some of the bigger wiki". We discussed about PendingChanges for more 2 years and get the overall consensus as result. We also translated all the message as required from similarity requests.

We understand that maybe the policy now is changed and will no any community have chance to be setup PendingChanges in future, except the available wikis which already have it. But at least there should be a clearly announcement about that. Thank you.

minhhuy added a comment.EditedApr 15 2020, 2:20 PM

Million years has passed, I wonder if our community could get any progession on this feature. We are still waiting...

Aklapper added a comment.Apr 15 2020, 2:37 PM

What I wrote in T204354#4644994

RhinosF1 subscribed.Apr 15 2020, 3:03 PM

Does https://meta.wikimedia.org/wiki/Limits_to_configuration_changes not means this is declinded?

Aklapper added a subtask: T185664: Code stewardship review: FlaggedRevs.May 16 2020, 5:30 PM
Stang removed a project: Wikimedia-Site-requests.Jul 17 2022, 6:52 PM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL