UDWiki:Administration/Re-Evaluations

Shortcut:
A/RE

Once a year, all sitting sysops will come up for re-evaluation by the community. The idea of this re-evaluation is to ensure that each 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 sysops have 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 a year, on Urban Dead's birthday (July 3rd), all sysops will be subject to a community discussion. Sysops may also put themselves up for re-evaluation at any time (see below). All users are asked to comment on each 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 two weeks, as all users get a chance to air their opinions on the candidate.

Once the two weeks are up, the Bureaucrats will review the community discussion and make a decision for each candidate based upon it. The user will be notified of the status of their re-evaluation, 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 themself 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 voicing 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 activity 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 qualifications may be used, these are just a few suggested things to consider before a user voices their opinion.

Re-Evaluations Being Discussed

Note: This round of A/REs began on July 11th, so comments will be open until July 25th.

A Helpful Little Gnome

• A Helpful Little Gnome (talk | contribs | UDWiki contribs | logs1 | logs2 | vndl data | sysop archive)

• Vouch - Absolute faith in AHLG as a sysop. DANCEDANCEREVOLUTION 00:49, 16 July 2019 (UTC)
• Vouch - Gnome is part of our inventory. -- Spiderzed▋ 20:05, 16 July 2019 (UTC)

DanceDanceRevolution

• DanceDanceRevolution (talk | contribs | UDWiki contribs | logs1 | logs2 | vndl data | sysop archive)
• Vouch - Among those up for RE, the most active one. And what we need at this stage are mostly warm bodies not asleep at the wheel. -- Spiderzed▋ 20:05, 16 July 2019 (UTC)

Rosslessness

• Rosslessness (talk | contribs | UDWiki contribs | logs1 | logs2 | vndl data | sysop archive)

• Vouch No combo to break Ross... I guess I just have to do a boring vouch. Ross as always has my complete faith as a sysop. DANCEDANCEREVOLUTION 00:49, 16 July 2019 (UTC)
• Abstain - Ross is fantastic when he is around, but it has been a while that he has been around. Will change to a Vouch if he reacts to the RE going on. -- Spiderzed▋ 20:05, 16 July 2019 (UTC)

Recent Re-Evaluations

See the 2018 Re-Evaluations

Archived Re-Evaluations

For earlier re-evaluations, see the following:

• This year's re-evaluations
• Last year's re-evaluations
• Sysop Archives for older re-evaluations and related sysop activities

Re-Evaluations Scheduling

User	Position	Last Contribution	Seat Available
A Helpful Little Gnome (Contribs)	Bureaucrat	2021-10-29	2021-12-01
DanceDanceRevolution (Contribs)	Bureaucrat	2021-10-28	2021-12-01
Rosslessness (Contribs)	Sysop	2024-06-10	N/A
Stelar (Contribs)	Sysop	2021-10-29	N/A

Total Sysops: 4 (excluding Kevan, LeakyBocks and Urbandead)

Last updated at: 03:58, 28 October 2021 (UTC)