Jump to content

Wikipedia talk:Requests for adminship/Archive 5

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Archive 1Archive 3Archive 4Archive 5Archive 6Archive 7Archive 10

Tim wants to distribute the task of making admins

I have half a mind to do away with this task, it gets tiresome after a while. Does anyone have any ideas on how the power to create sysops can be distributed to the user level? Say, with a quorum and a vote? -- Tim Starling 02:41, Jan 8, 2004 (UTC)

Automation suggested

Automate the process. Give them a request form where they enter the reason they want to become a sysop. Have seperate voting form which lists how long they have been here, their number of edits, and what reason they give. After exactly 2 weeks, if someone has less than a general consensus (let's say 80%) of the vote, they become a sysop. --Raul654 02:49, 8 Jan 2004 (UTC)

Let all admins do it and maintain a log

Why not just let any Admin promote and demote any user? Of course Admin candidates would have to go through the process of being listed here first and there would have to be a Promote/demote log in order to make sure Admins can't get away with making improper promotions/demotions. That way we don't have to depend on a developer to do this. --mav 02:54, 8 Jan 2004 (UTC)
Like IRC? Note that when I put forward my sysop blocking feature, a number of people were concerned that sysops would be able to block each other. It was only when I assured these people that this was not the case that they were happy with the implementation.
Speaking of IRC, Fuzheado and JeLuF said on #wikipedia that they'd prefer a quorum, say 3 required "signatures" to perform an operation. -- Tim Starling 06:17, Jan 8, 2004 (UTC)
Although I imagine mav's idea would be much be simpler and quicker to implement, I have to agree with the quorum idea. The one sysop (de)selects another idea is open to the possibility of mistakes (one sysop sysops a troll/vandal), a new form of "edit war", and abuse (nepotism). Foresight not being 20/20 I am not sure how serious these problems would be in practice but a quorom would certainly ameloriate them. Also having re-usable quorom code might well find uses elsewhere - although being efficient and automated like this might be considered unwiki :-) Pete/Pcb21 (talk) 09:06, 8 Jan 2004 (UTC)
Of course that is an even better idea! :) My concern was to easily implement something in the interim. I happen to trust that Admins ('sysop' is a user account switch not a person!) will use the ability with deliberate caution and only promote/demote accounts that have been confirmed via some process. In fact that may work so well that we don't need to implement technological ways to enforce that. Wikis are about trusting that most people will most often do good rather than evil. --mav 11:29, 8 Jan 2004 (UTC)
I'd say the idea is great, but maybe the quorum could be bumped up to 4 required signatures. I would not necessarily trust 2 signatures, 3 unspecified sysops is on the limit, but I would be more comfortable with 4 (and the explicit assumption that the act be performed in accordance with prior discussion here, only after the discussion clearly had settled down and reached a reasonably consensus conclusion). We have enough sysops nowadays that finding 4 public minded ones should not be insurmountable. -- Jussi-Ville Heiskanen 12:09, Jan 8, 2004 (UTC)

Ohh!

Ohh! Tim was talking about the task of actually granting the permissions. (Slaps forehead) --Raul654 02:58, 8 Jan 2004 (UTC)