UDWiki:Administration/Policy Discussion/Sysop Reevaluations

Overview

Every six 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

Sysops who wish to continue their System Operator status should note that before they can be re-evaluated, the following guidelines should be met by the candidate:

• Significant time within the community as a sysop.

We define this as the candidate has made at least one edit in the at least 3 months.

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.

• Significant activity within the community.

We define this as at least 500 edits in the past six months under the candidate's name.

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.

• Prior 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.

• 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.

• 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 user is highly exemplary in one criterion, a certain level of give may be extended to other criteria.

Once the candidate satisfies these guidelines and has reached their six month mark from their promotion to sysop, 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 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 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.

Summary

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 six 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 six months (i.e. new sysops can wait until their usual six month period, while the ones who are past their six months will have to cycle through).

• Current bureaucrats are exempt from this review process due to their own review process.

• This policy does not effect any account that Kevan may use as a wiki admin account, specifically:

• Kevan ‎

• Urbandead