Last modified: 2008-08-11 13:54:40 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 T17056, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 15056 - Disable FlaggedRevs custom configuration on Russian Wikipedia
Disable FlaggedRevs custom configuration on Russian Wikipedia
Status: RESOLVED INVALID
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
unspecified
All All
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
http://ru.wikipedia.org/wiki/Википеди...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-08-06 08:59 UTC by Dmitriy
Modified: 2008-08-11 13:54 UTC (History)
4 users (show)

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


Attachments

Description Dmitriy 2008-08-06 08:59:05 UTC
Please disable FlaggedRevs on Russian Wikipedia. One of the users misinformed the developers in his request to enable it.

In this poll
http://ru.wikipedia.org/wiki/Википедия:Опросы/О_выверке_статей
there were 76 votes/opinions for this feature and 65 votes/opinions against
this feature. Russian Wikipedia community is divided in opinions on this issue and has no consensus on this FlaggedRevs extension. Some users are strongly against it. In any case community did not approve it.
Comment 1 Obersachse 2008-08-06 09:20:04 UTC
Please, don't bring Russian Wikipedia's internal problems to bugzilla or somewhere else out of ruwiki itself. We are actively discussing it now, and will soon bring another poll (though we have already spent 2 ones before). There is no real need to disable it now. Thanks
Comment 2 Dmitriy 2008-08-06 09:28:22 UTC
Well, this problem was allready brought here by the people who rushed to enable this extension without community consensus. And there IS need to disable it right now as this very important Flaggedrev extension is used with total disregard for community opinion and without any rules and guidelines for using int.
Comment 3 Vladimir "Dr Bug" Medeyko 2008-08-06 16:42:06 UTC
Dear Dmitry (whoever you are), please abstain of attempts of pushing your own opinion. The further details on use flagged revision are now being discussed in Russian Wikipedia, and it's quite unlikely that you are not aware of this. Go there and express your fears to the community.

Developers are "servants", not "judges". Bugzilla is not a right place to complain about social processes in communities. If there is a decision by the community to disable FlaggedRevs on Russian Wikipedia, it would be disabled. Not earlier. 
Comment 4 Dmitriy 2008-08-07 00:52:17 UTC
Dear Vladimir. There was no decision by the community to enable it in the first place. Developers were misinformed by the 13-year --old teenager, who claimed that the consensus was reached, while this was not the case. Don't try to push YOUR own opinion.
Comment 5 Siebrand Mazeland 2008-08-10 23:39:01 UTC
Closed as INVALID based on information obtained in #wikimedia-ru. Please open a new issue in case the community would decide that the extension needs to be disabled.

[01:31] <siebrand> I am looking through bugzilla, and stumbled across a request to *disable* FlaggedRevs on ru.wp. Can you please give me some input? I tend to close 'INVALID' at the moment, because bugzilla is not the place for flame wars.
[01:31] <siebrand> https://bugzilla.wikimedia.org/show_bug.cgi?id=15056
[01:34] <grebenkov> siebrand: there is a request for comments running on russian wikipedia, which results are to show whether this extension should be left enabled or not
[01:34] <siebrand> grebenkov: so a *current* request to disable it is premature?
[01:36] <grebenkov> siebrand: yes, it is. until formal to disable it is reached (which I personally think is unlikely), no action should be taken
[01:36] <siebrand> grebenkov: OK, thank you. I will close the issue as invalid, advising to open a new issue once the consensus would be to disable it.
[01:37] <grebenkov> siebrand: yes, I think that would be the most appropriate course of action

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


Navigation
Links