Last modified: 2012-07-22 18:22:14 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 T35879, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 33879 - Give bureaucrats the ability to remove sysop rights at ro.wp
Give bureaucrats the ability to remove sysop rights at ro.wp
Status: RESOLVED INVALID
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
unspecified
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: community-consensus-needed
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-01-22 14:55 UTC by Strainu
Modified: 2012-07-22 18:22 UTC (History)
7 users (show)

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


Attachments

Description Strainu 2012-01-22 14:55:24 UTC
Per community discussion -
https://ro.wikipedia.org/wiki/Discu%C8%9Bie_Wikipedia:Administratori#Retragerea_permisiunilor_de_c.C4.83tre_birocra.C8.9Bi
- please give bureaucrats the ability to remove sysop rights at
the Romanian Wikipedia.
Comment 1 Snowolf 2012-03-17 09:21:35 UTC
I see comments from only 5 users, and rowiki has only 3 'crats. I strongly suggest that this is not advisable, especially given the recent hiwiki situation. This right should be enabled only in wikis with a significant number of 'crats where the potential for abuse is virtually none. I suggest that on such a small wiki it's highly unadvisable and should not be fullfilled.
Comment 2 Strainu 2012-03-17 20:50:45 UTC
5 users is a significant number on ro.wp. I have no idea what the hiwiki problem was, but I would say that we should have the right to risk an abuse if we wish to do so. I'm pretty sure removing the admin rights is something that can easily be undone by stewards if things really get out of hand. We have quite a high turnaround rate for administrators and asking for removal on meta just takes too long.
Comment 3 Snowolf 2012-03-18 06:27:50 UTC
5 votes are not even considered enough to appoint a local 'crat so they most certainly shouldn't be enough for such a change.
Comment 4 Dan Collins 2012-03-18 07:00:00 UTC
Greetings,

There does not appear to be local consensus, but feel free to discuss that here. If you want to discuss this on the merits, please go to http://meta.wikimedia.org/wiki/Talk:Limits_to_configuration_changes#Disconnection_from_stewards_overseeing so that we can have discussions on this in a centralized location.
Comment 5 Strainu 2012-03-18 11:12:16 UTC
(In reply to comment #3)
> 5 votes are not even considered enough to appoint a local 'crat so they most
> certainly shouldn't be enough for such a change.

How in the name of god did you figured that out? Perhaps you're talking about some meta limit, which does not directly applies to ro.wp. There is currently no limit to the number of votes needed to be appointed on ro.wp.
Comment 6 Tim Weyer 2012-03-18 11:30:34 UTC
With all due respect, but the ability to deadministrate users should be reserved for stewards and bureaucrats on big wikis with many administrators like enwiki and dewiki. I count 25 administrators on rowiki ( https://ro.wikipedia.org/wiki/Special:List%C4%83_utilizatori/sysop ).
Comment 7 Dereckson 2012-03-18 12:39:58 UTC
Taking in consideartion the lack of projects-wide policy, and the reticences of people to open such a policy (cf. bug ), I doubt we can say "the ability to deadministrate users should be 
reserved for stewards and bureaucrats on big wikis with many administrators".

See also http://meta.wikimedia.org/wiki/Talk:Limits_to_configuration_changes#Disconnection_from_stewards_overseeing
Comment 8 matanya 2012-07-22 17:57:42 UTC
As this isn't clear per policy, and bugzilla isn't the place to discuss such a policy, I'll close this bug as won't fix for now, until there is a clear policy.
Comment 9 Alex Monk 2012-07-22 18:13:20 UTC
This isn't prohibited by any policy to my knowledge. There are some members of the community who think that somehow only stewards should be able to do this. What they think of it is irrelevant unless they can get enough support to change the global policy.

I'm not going to reopen this bug because there doesn't appear to be community consensus for the change (there are no 'no' votes but the number of people participating is not nearly enough, WONTFIX -> INVALID), but please ignore comments 6 and 8.
Comment 10 Alex Monk 2012-07-22 18:22:14 UTC
After some discussion it turns out I completely misunderstood Matanya's comment.

It seems that he meant there was no clear policy for determining whether this change has local community consensus. Don't ignore that. :)

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


Navigation
Links