Last modified: 2008-03-25 21:05:49 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 13503 - On alswiki, allow bureaucrats to remove sysop
On alswiki, allow bureaucrats to remove sysop
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: shell
Depends on:
  Show dependency treegraph
Reported: 2008-03-25 18:36 UTC by Melancholie
Modified: 2008-03-25 21:05 UTC (History)
3 users (show)

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


Description Melancholie 2008-03-25 18:36:35 UTC
Although being bureaucrat on als.wp I cannot remove 'sysop' rights at [[:als:Special:Userrights]]! Only 'bot' and 'bureaucrat' is shown an accepted at all. Is this intended? I sysoped my Bot for easily creating a global, unified login account (single user login), now I cannot desysop that account (Bots should not really have sysop rights, I think ;-)

I will have to keep the 'bot' flag removed as long as this bug isn't fixed, so please...

See [[:als:Spezial:Benutzerrechte/MelancholieBot]]
Comment 1 Majorly 2008-03-25 18:42:55 UTC
This is not a bug. Bureaucrats can only add sysop/bureaucrat and not remove, but they can add and remove bots. You will need to contact a steward on [[meta:Requests for permissions]] to remove it.
Comment 2 Aryeh Gregor (not reading bugmail, please e-mail directly) 2008-03-25 18:45:14 UTC
Bureaucrats would presumably be able to remove sysop on a given project if there were consensus on that project.  At least, I've heard nothing to the contrary.  So I'm reclosing as LATER: demonstrate consensus and presumably this can be enabled for your project.
Comment 3 Brion Vibber 2008-03-25 18:50:29 UTC
This is a serious abuse of bureaucrat privileges -- false sysopping of this sort may lead to loss of your privileges.
Comment 4 Umschattiger 2008-03-25 20:13:36 UTC
> This is a serious abuse of bureaucrat privileges -- false sysopping of this
> sort may lead to loss of your privileges.

it may have been wiser not to do this, but I wouldn't say that this is a serious (!) abuse. Melancholie used his privilege in this case only for test purposes (SUL) I assume and didn't intend to harm anyone / anything. And btw, Melancholie is our one and only bureaucrat...

De-Sysop of Melancholie-Bot strongly supported

give de-sysop-rights to Melancholie not desired (no need to)

greets, Umschattiger, sysop als
Comment 5 Melancholie 2008-03-25 21:05:49 UTC
@Majorly: See
@Simetrical: No need for allowing bureaucrats to remove sysop on
@Brion: Do you have a link (policy)? I have been sysop and bureaucrat on als.wp etc. for many many years now. Where is written that a sysop is not allowed to have two sysop accounts (and in this case only accidently!) Furthermore I myself removed the bot flag from that account *right after* posting this report (#13503), see The account was furthermore blocked there. "MelancholieBot" does not have sysop rights on *any other* wiki, no edits were made as sysop (seeäge/MelancholieBot) and myself informed you about this problem, I didn't want either.

You do allow all sysops to unify their accounts (SUL) now, and nothing more I did in this case; User:Melancholie and User:MelancholieBot is one the same person! No abuse, just knowledge of how to get legitimate things done easily (why only sysops may may get single user login accounts, I thought). I (a person) was voted towards a sysop. I didn't give any other person sysop rights. No abuse, sorry!

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