danny.leinad wrote:

FYI: FlaggedRevs allow grant "editor" flag, not "patroller".

DimpleO wrote:

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.

DimpleO wrote:

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?

DimpleO wrote:

Haaallooo, anybody here?

(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.

DimpleO wrote:

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

Is the review status of a revision just binary (accepted or unaccepted)?

DimpleO wrote:

Yes, exactly, the extra options are not needed.

So we have:
$wgFlaggedRevsNamespaces[] = NS_CATEGORY;
$wgFlaggedRevsOverride = false;
$wgFlaggedRevTags['accuracy']['levels'] = 1;
$wgFlaggedRevsAutopromote = false;

CC'd rob.

DimpleO wrote:

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

(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.

DimpleO wrote:

Yeah, I understood:). Thanks for the clarification. Then everything is correct.

Aaron, is there anything else left to get this done?

(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.

jeluf wrote:

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;
+
}

jeluf wrote:

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

1. * edit flaggedrevs.dblist
2. * touch InitialiseSettings.php to invalidate the cache
3. * sync-common-all

You can find the entire config file at
http://noc.wikimedia.org/conf/highlight.php?file=InitialiseSettings.php

DimpleO wrote:

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

jeluf wrote:

Who should get autoeditor privs? sysops?

DimpleO wrote:

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.

(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?

stasielvova wrote:

(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.

Done, except for bcrats. Are there non-sysop bcrats that need this and can't just get the sysop group?

stasielvova wrote:

I think no, bcrats was the context 'even bcrats haven't this right!' :) Thank you!

stasielvova wrote:

And what's about Special:Stableversions?

(In reply to comment #24)

And what's about Special:Stableversions?

This should be done already. Does it not show?

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).

DimpleO wrote:

Dear Aaron Schulz, thank you very much, now we are all working, and this application may be closed :).

DimpleO wrote:

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?

Olya, please open a new bug report! :o)