Last modified: 2011-05-20 21:08:17 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T27438, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 25438 - Enable FlaggedRevs for Belarussian Wikipedia
Enable FlaggedRevs for Belarussian Wikipedia
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Aaron Schulz
http://be.wikipedia.org/w/index.php?o...
: shell
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-10-06 18:51 UTC by Olya
Modified: 2011-05-20 21:08 UTC (History)
8 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Olya 2010-10-06 18:51:31 UTC
Please enable FlaggedRevs extension for Belarusian Wikipedia.

We have discussed the inclusion of applications for our section, and since nobody was against, the vote decided not to pursue. Discussion went on here - http://be.wikipedia.org/wiki/Вікіпедыя_размовы:Догляд

We have a bureaucrat (user: Maksіm L.) and 3 Admin (user: Maksіm L., user: Hamelka, user: JerzyKundrat). We would like to have these people were right to assign a flag "Patroller".

Thanks in advance, Homelka
Comment 1 Leinad 2010-10-06 22:18:54 UTC
FYI: FlaggedRevs allow grant "editor" flag, not "patroller".
Comment 2 Olya 2010-10-07 07:07:40 UTC
You're right, it's my fault, of course, "editor".

My translator incorrectly translated the nicknames of users. That's right - Хомелка, JerzyKundrat & Maksіm L.
Comment 3 Olya 2010-11-27 15:02:45 UTC
Good afternoon. We have made a request to switch on FlaggedRevs almost 2 months ago, but this is not done until now. May I know what the problem is and whether we can hope for a speedy solution to this problem?
Comment 4 Olya 2010-12-09 19:31:12 UTC
Haaallooo, anybody here?
Comment 5 Aaron Schulz 2010-12-09 19:44:28 UTC
(In reply to comment #4)
> Haaallooo, anybody here?

This just crossed by radar, so I'll pick it up.

A few questions:
(i) What namespaces should this be for? The default is (main pages,templates,images)
(ii) Should stable versions show to readers or should the latest version show?

Also, with only a few users with admin/review rights on a small wiki, has the effect on participation been discussed? Instant gratification of edits going "live" is more important smaller projects (at least I think so). This relates to (ii) above.

I'd also assume that wgFlaggedRevsAutopromote is disabled.
Comment 6 Olya 2010-12-10 19:23:55 UTC
Good afternoon, discussions on connecting of the mechanism was carried out extensively, including virtual and real meetings on the wiki, just not satisfied with the vote because there was no objecting. Therefore, we can include it safely.
About your questions.

FlaggedRevs should be enabled in those namespaces that you listed (main
pages, templates, images) + category, if possible.

Readers will display the latest version of the page, indicating that it is not stable and with a link to a stable version.

wgFlaggedRevsAutopromoteshould be disabled, because in each case the flag will be assigned by the voting community.

Thank you
Comment 7 Aaron Schulz 2010-12-11 19:21:38 UTC
Is the review status of a revision just binary (accepted or unaccepted)?
Comment 8 Olya 2010-12-11 21:37:18 UTC
Yes, exactly, the extra options are not needed.
Comment 9 Aaron Schulz 2010-12-11 22:06:43 UTC
So we have:
$wgFlaggedRevsNamespaces[] = NS_CATEGORY;
$wgFlaggedRevsOverride = false;
$wgFlaggedRevTags['accuracy']['levels'] = 1;
$wgFlaggedRevsAutopromote = false;

CC'd rob.
Comment 10 Olya 2010-12-12 09:37:26 UTC
As far as I know in programming:), all right

Only said that about namespaces correctly:

$wgFlaggedRevsNamespaces[] = NS_CATEGORY
$wgFlaggedRevsNamespaces[] = NS_MAIN
$wgFlaggedRevsNamespaces[] = NS_TEMPLATE
$wgFlaggedRevsNamespaces[] = NS_IMAGE
Comment 11 Aaron Schulz 2010-12-12 12:59:56 UTC
(In reply to comment #10)
> As far as I know in programming:), all right
> 
> Only said that about namespaces correctly:
> 
> $wgFlaggedRevsNamespaces[] = NS_CATEGORY
> $wgFlaggedRevsNamespaces[] = NS_MAIN
> $wgFlaggedRevsNamespaces[] = NS_TEMPLATE
> $wgFlaggedRevsNamespaces[] = NS_IMAGE

main/template/image are in wgFlaggedRevsNamespaces by default. We only need to append category to it in wmf-config/flaggedrevs.php.
Comment 12 Olya 2010-12-12 15:22:26 UTC
Yeah, I understood:). Thanks for the clarification. Then everything is correct.
Comment 13 Mark A. Hershberger 2011-01-19 20:22:07 UTC
Aaron, is there anything else left to get this done?
Comment 14 Aaron Schulz 2011-01-19 22:13:02 UTC
(In reply to comment #13)
> Aaron, is there anything else left to get this done?

Rob was doing the shell part of these for a while, so I was kind of waiting on him. AFAIK, he's working on other stuff probably.

I can do this myself over Fri-Sun though.
Comment 15 JeLuF 2011-02-03 21:37:57 UTC
Index: flaggedrevs.php
===================================================================
--- flaggedrevs.php     (revision 1562)
+++ flaggedrevs.php     (working copy)
@@ -493,6 +493,12 @@
        $wgRemoveGroups['bureaucrat'][] = 'reviewer';
        $wgAddGroups['bureaucrat'][] = 'editor';
        $wgRemoveGroups['bureaucrat'][] = 'editor';
+} elseif ( $wgDBname == 'bewiki' ) {
+       $wgFlaggedRevsNamespaces[] = NS_CATEGORY;
+       $wgFlaggedRevsOverride = false;
+       $wgFlaggedRevTags['accuracy']['levels'] = 1;
+       $wgFlaggedRevsAutopromote = false;
+
 }
Comment 16 JeLuF 2011-02-03 21:38:13 UTC
Your change has been completed.
Please reopen this ticket if anything went wrong.
The following configuration settings have been changed:
===================================================================
Index: InitialiseSettings.php
===================================================================
--- InitialiseSettings.php	(revision 1563)
+++ InitialiseSettings.php	(working copy)
@@ -8119,7 +8119,7 @@
     'default' => false,
     # To update this dblist:
     #   * ADD THE TABLES TO THE DATABASE
-    #       e.g. php maintenance/sql.php --wiki=WIKINAME extensions/FlaggedRevs/FlaggedRevs.sql
+    #        e.g. php maintenance/sql.php --wiki=WIKINAME extensions/FlaggedRevs/FlaggedRevs.sql
     #   * edit flaggedrevs.dblist
     #   * touch InitialiseSettings.php to invalidate the cache
     #   * sync-common-all
===================================================================
You can find the entire config file at
http://noc.wikimedia.org/conf/highlight.php?file=InitialiseSettings.php
Comment 17 Olya 2011-02-05 13:03:07 UTC
Many thanks for your work. We are very pleased with the result. But we expect that will also include the option autoeditors. It can also be included? Thank you
Comment 18 JeLuF 2011-02-05 13:11:14 UTC
Who should get autoeditor privs? sysops?
Comment 19 Olya 2011-02-05 18:55:02 UTC
The rights of autoeditors must be issued by administrators to address community. 

Problem number 2: the situation is such that none of our section could not establish a stable version of the article. Even administrators and bureaucrats, says that we are not enough rights.
Comment 20 Aaron Schulz 2011-03-25 01:15:18 UTC
(In reply to comment #19)
> Problem number 2: the situation is such that none of our section could not
> establish a stable version of the article. Even administrators and bureaucrats,
> says that we are not enough rights.
>
Hmm, could you elaborate on this?

(In reply to comment #19)
> The rights of autoeditors must be issued by administrators to address
> community. 
>
So 'autoeditor' is to be a group with just the 'autoreview' right and admins are able to grant and remove the group?
Comment 21 Lvova 2011-03-31 09:17:53 UTC
(In reply to comment #20)
Olya asked me to help with the answer.

> > Problem number 2: the situation is such that none of our section could not establish a stable version of the article. Even administrators and bureaucrats, says that we are not enough rights.
> Hmm, could you elaborate on this?
In ru.wiki our sysops can change the settings of the displayed version for the every single page. By default we display the lastest version but we display the lastest REVIEWED version for good and featured articles. We call it 'the stable version' (Special:Stableversions, you know), and be.wiki users want this option too.

> > The rights of autoeditors must be issued by administrators to address
> > community. 
> So 'autoeditor' is to be a group with just the 'autoreview' right and admins
> are able to grant and remove the group?
Yes, they want to add a group of users with 'autoreview' rights that will be given by sysops and bcrats, without automatic user promotion.
Comment 22 Aaron Schulz 2011-03-31 14:52:42 UTC
Done, except for bcrats. Are there non-sysop bcrats that need this and can't just get the sysop group?
Comment 23 Lvova 2011-03-31 16:52:11 UTC
I think no, bcrats was the context 'even bcrats haven't this right!' :) Thank you!
Comment 24 Lvova 2011-03-31 19:57:09 UTC
And what's about Special:Stableversions?
Comment 25 Aaron Schulz 2011-03-31 20:02:44 UTC
(In reply to comment #24)
> And what's about Special:Stableversions?

This should be done already. Does it not show?
Comment 26 Aaron Schulz 2011-03-31 20:05:08 UTC
I think you mean Special:Stabilization. Pressing "protect" tab of a page should show a link to set the options about the default version (above the edit/move options).
Comment 27 Olya 2011-04-01 08:25:01 UTC
Dear Aaron Schulz, thank you very much, now we are all working, and this application may be closed :).
Comment 28 Olya 2011-05-20 20:14:08 UTC
Hello. [http://be.wikipedia.org/wiki/%D0%90%D0%B4%D0%BC%D1%8B%D1%81%D0%BB%D0%BE%D0%B2%D0%B0%D0%B5:ValidationStatistics We have a problem.] Since May 17 is not updated statistics. You can do something with this, please?
Comment 29 Antoine "hashar" Musso (WMF) 2011-05-20 21:08:17 UTC
Olya, please open a new bug report! :o)

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links