UDWiki:Administration/Policy Discussion/Sysop Reevaluations

From The Urban Dead Wiki
Jump to navigationJump to search
Green check.png Guidelines — Policy Document
This page is a statement of official UDWiki Policies and Rules. See Policy Discussion for policy additions and changes.
Padlock.png Administration Services — Protection.
This page has been protected against editing. See the archive of recent actions or the Protections log.
A more recent policy has altered the frequency of mandatory sysop re-evaluations. In addition to voluntary re-evaluations, all sysops are now simultaneously re-evaluated annually beginning on July the 3rd.


Every Eight months from when a user is nominated to be a sysop, that user will come up for a re-evaluation by the community. The idea of this re-evaluation is to ensure that the sysop still has the trust of the community, which is vital for a sysop to have. This will give the community a chance to voice their opinions about how the sysop has been doing, and re-affirm or decline their trusted user status.

The idea of a sysop being a trusted user is a part of the guidelines for the general conduct of a sysop. The guidelines for the re-evaluation is the same as for being promoted to a sysop (which is reposted below), but with a few minor changes in wording.

Guidelines for System Operator Re-Evaluations

Once the candidate has reached their eight month mark from their promotion to sysop or put themselves up for re-evaluation (see below), the user is then subject to a community discussion. All users are asked to comment on the candidate in question, ask questions of the candidate, and discuss the candidate's suitability for continuing to be a System Operator. This is not a vote. It is instead merely a request for comments from the wiki community. This will continue for one week, as all users get a chance to air their opinions on the candidate. The reason for only one week for discussions is due to the high-profile nature of the sysops, and most users should be familiar with them.

Once the one week is up, the Bureaucrats will review the community discussion and make a decision based upon it. The user will be notified of the status of their request, and will be retained in their position should it appear that the community is willing to continue to accept them as a System Operator. In the event that the decision is negative, then the sysop will be demoted back to regular user status, where after a month's time, the user can re-submit themselves for promotion.

Before users voice their opinions on the candidate who wishes to continue their System Operator status, the following guidelines should be reviewed by the user:

General User Guidelines for System Operator Re-Evaluations

Before vocing their opinion on a candidate's re-evaluation bid, a user should consider some of the following questions:

  • Has the candidate spent significant time within the community as a sysop?
We define this as the candidate having made at least one edit in the past 3 months. It is recommended that a user look over the the sysop activity check and last 500 edits to determine the level of acivity of the candidate.
Note: The Truly Inactive Sysops policy dictates that a sysop who hasn't made an edit within four months is automatically demoted. Therefore, for a sysop to be re-evaluated, they need to have made an edit before that time-frame is up.
  • Has the candidate maintained significant activity within the community?
We define this as at least 50 edits under the candidate's name since their last re-evaluation. It is recommended that a user look over the candidate's last 50 edits in order to get a feel for the activity of a candidate.
Note: looking in a User's User contributions might give false results for this criterion, as the edit history used to be periodically purged on this wiki.
  • Has the candidate expressed interest in maintaining the community?
We define this as clear evidence that the candidate is already performing maintenance tasks and continuing taking a leadership role on the wiki.
  • Has the candidate expressed a desire to continue to be a System Operator.
We define this simply as indicating in the candidate's request their desire to continue to maintain the position.
  • Is there an indication of trust in the candidate.
We define this as a minimum of three other users (preferably users with at least 200 edits under their name and at least one System Operator), willing to vouch for the candidate's suitability for the role.

If a candidate is highly exemplary in one guideline, a certain level of flexibility should be extended to the other guidelines. Other guidelines for qualifcations may be used, these are just a few suggested things to consider before a user voices their opinion.

Nuts and Bolts

A new page for the re-evaluations will be created in order to keep it separate from the regular promotions. The new page will be A/RE. An archive of re-evaluations will be created similar to the archiving system of the promotions page. On the re-evaluations page, a section similar to the sysop activity check will be created to give users advanced notice as to when each sysop is up for re-evaluation to compensate for the reduced time and to let people know ahead of time when each sysop is up for re-evaluation.

Voluntary Sysop Re-Evaluation

A sysop can request a voluntary re-evaluation provided it has been at least four months since their last re-evaluation. The reason for waiting at least four months between evaluations is to prevent the possibility of a sysop constantly putting themselves up for re-evaluation. The guidelines for a voluntary re-evaluation is the same as a normal re-evaluation.

Bureaucrats and Re-evaluations

The bureaucrat's promotions process is in essence a re-evaluation of a sysop by the community. Bureaucrats go through regular process of re-elections, so each time they are elected, the community is renewing their faith in the sysop, and is not subject to re-evaluation through this policy. When a bureaucrat is not re-elected and becomes a sysop again, then the sysop is again available for re-evaluation through this policy. When this happens, the bureaucrat's eight months start from when they were promoted to bureaucrat.


  • User A is promoted to sysop on April 12th, 2009. User A's date for re-evaluation is December 12th, 2009. In their time as a sysop, User A is elected to being a bureaucrat on July 24th, 2009. For as long as they are re-elected to the bureaucrat position, their re-evaluation is delayed (due to the bureaucrat promotion process effectively being a re-evaluation by the community).
  • User B is a bureaucrat and was elected to the position on July 22nd, 2009. Unfortunately, they serve their term for six months and at re-election, they are not re-elected to the position. This means that their last re-evaluation is effectively July 22nd 2009 (due to the bureaucrat promotion process effectively being a re-evaluation by the community), and their new re-evaluation date is March 22nd, 2010.


This policy creates a system for the community to reaffirm the trust in the sysop (much like Bureaucrats have to):

  • Every sysop will be re-evaluated by the community once their eight month mark comes up.
  • This will start with whomever has been a sysop the longest, and every two weeks thereafter the next longest sysop without a re-evaluation will come up for review until everyone has had one or falls short of their eight months (i.e. new sysops can wait until their usual eight month period, while the ones who are past their eight months will have to cycle through).
  • This policy does not effect any account that Kevan may use as a wiki admin account, specifically:

Voting Section

Voting Rules
Votes must be numbered, signed, and timestamped. They can take one of two forms:
  • # comments ~~~~
  • # ~~~~

Votes that do not conform to the above will be struck by a sysop.

The only valid voting sections are For and Against. If you wish to abstain from voting, do not vote.


  1. Author vote. --Akule Maker of fine, hand-crafted UDWiki sass since 2006 -- Akule School's back in session™ 22:12, 4 August 2009 (BST)
  2. Bob Boberton TF / DW Littlemudkipsig.gif 22:17, 4 August 2009 (BST)
  3. - I haven't read much past the summary but I assume it does what it says it does, giving the community the power to demote awful sysops and uselessness ones like Daranz, Swiers and Thari. Though I find 8 months a bit too long personally, that's a long time in which a bad sysops can do allot of bad things. --Thadeous Oakley 22:17, 4 August 2009 (BST)
    swiers never wanted to be a sysop. He only wanted the tools that come with the rank. He was always honest about this, and the community trusted him this tools, and i dont see why someone like you should be against him. --People's Commissar Hagnat [talk] [wcdz] 00:52, 5 August 2009 (BST)
    Swiers was useless? hah! All that work he didn't do on Iwitness? Oh. No wait. --RosslessnessWant a Location Image? 10:07, 5 August 2009 (BST)
    I beg you pardon? What has Iwitness to do with sysops duties? I'm sure he is doing a great job with that, and that he was a great wiki contributor, otherwise he wouldn't be a sysops in the first place. Right now however, I don't see any evidence he is doing anything with his sysops status or his tools, or being active at all in the wiki. --Thadeous Oakley 17:17, 5 August 2009 (BST)
    My pardon is begged. Instead of uselesness you should have said Inactive. Which is why he's only got 23 days left until his final demotion warning. --RosslessnessWant a Location Image? 17:34, 5 August 2009 (BST)
    What fucking sysopy shit did he ever do? You know, when the goons were tearing shit up on here he was a sysop and "active" and he never once fucking stuck his head in to A/VB. I know, because I was on there all the time. By your logic Iscariot is a great sysop (was rather) since he did all kinds of work on Recruitment and those other shitty groups he made. And he was on A/VB more! --Globetrotters Icon.png #99 DCC 23:03, 7 August 2009 (BST)
    Welcome back DCC. --RosslessnessWant a Location Image? 23:36, 7 August 2009 (BST)
    By work you mean tried to game the system and threw a fit when he got called on it right? --Karekmaps?! 04:37, 9 August 2009 (BST)
    I meant being the VOICE OF THE COMMUNITY! Being on that cross is so hard.--Globetrotters Icon.png #99 DCC 12:02, 9 August 2009 (BST)
  4. Definitely Needed --THE Godfather of Яesensitized, Anime Sucks Yalk | W! U! WMM| CC CPFOAS DORISFlag.jpg LOE ZHU | Яezzens 23:18, 4 August 2009 (BST)
  5. Yup --Banana reads Scoundrell for all of Yesterday's News, Today! 23:27, 4 August 2009 (BST)
  6. Very much needed.-- Adward  23:29, 4 August 2009 (BST)
  7. Every 4 months. 1/3 of the year. --Sonny Corleone DORIS I jizzed in my pants pr0n 23:52, 4 August 2009 (BST)
    A third of the year is far too short. Means we'll have pretty much constant reevaluations. Personally, I think that eight months is too short, and we should have it once a year, but consensus on the talk page was against me. Linkthewindow  Talk  07:48, 5 August 2009 (BST)
  8. --Paddy DignamIS DEAD 00:08, 5 August 2009 (BST)
  9. -Although Daranz is a friend of Kevan's and likely wont be affected, and although this has the potential to be misused... I have to be for it. Conndrakamod TAZM CFT 00:34, 5 August 2009 (BST)
    You realize that you won't survive the chopping block, Connie? It's like the cows walking up the ramp to the slaughthouse saying well, at least we are getting some fresh air for once. You poor poor cow.--Globetrotters Icon.png #99 DCC 23:03, 7 August 2009 (BST)
  10. i usually was against sysop reevaluation policies... but heck, this was really well written. --People's Commissar Hagnat [talk] [wcdz] 00:52, 5 August 2009 (BST)
    Way to support something that can no longer affect you! Cutting Edge!! --Globetrotters Icon.png #99 DCC 23:03, 7 August 2009 (BST)
  11. Yes, very much so. The trust of the community is important for a sysop to do their job, and it would be fantastic if the community got a voice. --User:Axe27/Sig 01:22, 5 August 2009 (BST)
    The community has a voice - it's WHINE WHINE WHINE. --Globetrotters Icon.png #99 DCC 23:03, 7 August 2009 (BST)
  12. --MTRemick T | C | Fey | NBC 01:55, 5 August 2009 (BST)
  13. As per Sonny, 1/3rd of the year is nice. -- Emot-argh.gif 02:26, 5 August 2009 (BST)
  14. This has no teeth, since the reevaluation doesn't involve votes, just "input". The sysops will still have the ability to do whatever they want regardless of community opinion. But it's better than nothing.--GANG Giles Sednik CAPD 02:50, 5 August 2009 (BST)
    That's brilliant. "This won't work, but I like it anyway!" Then why not fucking write something that will work and stir up some real community support? --Globetrotters Icon.png #99 DCC 23:03, 7 August 2009 (BST)
  15. --ϑϑ 03:13, 5 August 2009 (BST)
  16. Fantastic. The whole point of having bureaucrats is so people can trust them to make exactly these kinds of decisions fairly. Stoked about it being A/RE! Cyberbob  Talk  04:16, 5 August 2009 (BST)
    Now just make sure you keep the good crats in office! Otherwise you are back to square one. --Globetrotters Icon.png #99 DCC 23:03, 7 August 2009 (BST)
  17. As Bob. Oh, and Giles, we've gone through why votes are a bad thing, and why it doesn't have to be a vote on the talk page for weeks now. But, yeah, this means that sysops can't be in the job "for life," and also means that the community can give feedback to good sysops, and show bad sysops the door. However, it doesn't give power solely to the community, and thus eliminates the chance of misinformed votes, meatpuppetry or personal vendettas meaning the demotion of an otherwise good sysop. Linkthewindow  Talk  07:45, 5 August 2009 (BST)
    Sysops can't be in the position for life anyway, and you're bascially ignoring the history of promotions bid to make the rest of that point. --Karekmaps?! 09:26, 5 August 2009 (BST)
  18. Why the hell isn't it 9 months! But whatever. Surely I'll have asked for demotion by 8 months anyway. --RosslessnessWant a Location Image? 10:08, 5 August 2009 (BST)
  19. -- User:The Rooster RoosterDragon User talk:The Rooster 17:39, 5 August 2009 (BST)
  20. I have to vote for because it is better than nothing but the outrageously low bar on contribs (50 in 8 months, what the fuck?) and they way that the whole 'we define' thing makes it seem like the vouching has nothing to do with it and the crats will just be seeing if the op has ticked the boxes and has 3 (wow) vouches.--xoxo 01:00, 6 August 2009 (BST)
  21. Glad we finally have a workable review process. --Darth Sensitive Talk W! 00:18, 9 August 2009 (BST)
    Except you don't, you just have the one they think they can pass. That's what a sizable amount of the talk page discussion is about, even the project authors essentially admitted as much. --Karekmaps?! 04:40, 9 August 2009 (BST)
  22. Slightly better than nothing. --WanYao 13:06, 12 August 2009 (BST)
  23. Not perfect but its a step in the right direction --DOWN WITH THE 'CRATS!!! | Join Nod!!! 21:53, 14 August 2009 (BST)
  24. I alzo iz spaking "YEA!" fore diz. (DCC - shaddupfergodzakealready!) --Funt Solo QT Scotland flag.JPG 21:23, 17 August 2009 (BST)


  1. Against for 2 very minor points. 1) on reflection I think 9 months would be best (or at the very least date the evaluation from the close of their bid) 2) the Crat evaluation section needs a clarification to clearly state that it is from their last Crat election... Boxy cannot be the only Crat to have stayed in the role more than 8 months. The wording here means he would have immediately faced a re-evaluation on losing the position. --Honestmistake 00:09, 5 August 2009 (BST)
    The 'wording' says the exact opposite. A Crat's re-election comes when they are demoted from Crat + 8 months. --ϑϑ 03:12, 5 August 2009 (BST)
    The 'wording' says nothing of the sort "When this happens, the bureaucrat's eight months start from when they were promoted to bureaucrat." As it currently reads, any Crat who serves 3 or more terms would face A/RE as soon as they become normal Sysops. "I believe it should read that their 8 months start from their last successful Crat Promotion" --Honestmistake 08:09, 5 August 2009 (BST)
  2. All I read was more forced drama and more bureaucracy here. All this will be is an unnecessary popularity contest, because if a sysop is doing their job horrible enough they will be put up in Misconduct and should be demoted. Whether or not that system works is another issue.--SirArgo Talk 00:16, 5 August 2009 (BST)
    Yeah, but misconduct has NO way to demote and instead of actually tacking demotion onto something that it should be with they are writing up a little Kum-Ba-Yah fuck me hug box that won't really do anything. Bureacracy wins again! Where the fuck is Grim when you need him? --Globetrotters Icon.png #99 DCC 23:03, 7 August 2009 (BST)
  3. Against - Because policies that aren't done right because it'd be "too hard" are about as bad as policies done wrong for the wrong reasons. This'll just get in the way of actually fixing the system and providing the desired result like oh so many policies before have done with things like Arbitration. --Karekmaps?! 02:17, 5 August 2009 (BST)
  4. Against Re-evaluation should be based on Misconduct not some random "vote".--– Nubis NWO 03:37, 6 August 2009 (BST)
    Word.--Globetrotters Icon.png #99 DCC 23:03, 7 August 2009 (BST)
  5. Against - "We define this as at least 50 edits under the candidate's name since their last re-evaluation." - Far to low a number. --Haliman - Talk 23:42, 7 August 2009 (BST)
    I don't understand what you mean by 'far to low a number' it appears to be nonsensical goodsir! --xoxo 01:07, 8 August 2009 (BST)
    AGrees with J3D --DOWN WITH THE 'CRATS!!! | Join Nod!!! 21:44, 14 August 2009 (BST)
  6. Against - As Karek and Nubis. -- Cheese 23:40, 12 August 2009 (BST)