Atkinspedia:Administrators

From Atkinspedia

Administrators are Atkinspedians who have access to technical features that help with maintenance. Those include protecting and deleting pages, blocking other editors, and undoing these actions as well. Atkinspedia practice is to grant this access to anyone who has been an active and regular Atkinspedia contributor for a while, is familiar with and respects Atkinspedia policy, and is generally a known and trusted member of the community.

In the early days of Atkinspedia all users acted as administrators and in principle they still should. Any user can behave as if they are an administrator (provided they do not falsely claim to be one), even if they have not been given the extra administrative functions. Users doing so are more likely to be nominated as full administrators by members of the community and more likely to be chosen when they are finally nominated. From early on, it has been pointed out that administrators should never develop into a special subgroup of the community, but should be a part of the community like anyone else only equipped with a few more tools to do some chores that would potentially be harmful if everyone was entrusted with them. In practice, standards to getting appointed administrator have risen but there are still several administrators created every week.

The community does look to administrators to perform essential housekeeping chores that require the extra access administrators are entrusted with. Among them are watching the Articles for deletion debates and carrying out the consensus of the community on keeping or deleting these articles, keeping an eye on new and changed articles to swiftly delete obvious vandalism, and meeting user requests for help that require administrative access. Since administrators are expected to be experienced members of the community, users seeking help will often turn to an administrator for advice and information. In general, administrators acting in this role are neutral. They do not have any direct involvement in the issues they are helping people with.

Contents 1 So, what's the deal? 1.1 Protected pages 1.2 Deletion and undeletion 1.3 Block and unblock 1.4 Reverting 1.5 Enforcement of Arbitration Committee rulings 1.6 Hiding vandalism from recent changes 1.7 Design and wording of the interface 1.8 Other 2 Becoming an administrator 3 Places where admins in particular can assist 4 Other access types 4.1 IP addresses 4.2 Signed-in users 4.3 Bots 4.4 Bureaucrats 4.5 Stewards 4.6 Developers 5 Administrator abuse 6 Dealing with grievances

So, what's the deal?

The wiki software has a few important features that are restricted. Of those restricted features, administrators have access to the following. (New admins, see Atkinspedia:Administrators' how-to guide.)

Protected pages

• Edit the Main Page, and other protected pages. For information and guidelines, see Atkinspedia:Editing the main page. You can suggest changes at Talk:Main Page. The main page used to receive a lot of vandalism; protecting it is an unfortunate compromise to keep our welcome mat free of random profanity.

• Protect and unprotect pages. Pages are only protected in certain rare circumstances - for information and guidelines, see Atkinspedia:Protection policy. This also includes the ability to use semi-protection.

Deletion and undeletion

• Delete pages, including images, and their history. For information and guidelines, see both Atkinspedia:Deletion policy and (most definitely) Atkinspedia:Deletion guidelines for administrators. To suggest a page for deletion (after reading the policy and guidelines pages!), see Atkinspedia:Articles for deletion. Sometimes deletion is a technical matter, in which a redirection page has to be removed to make way for renaming an article, or a page whose history has been broken up has to be deleted and the pieces recombined. Other times it's a matter of cleaning up simple junk edits on pages with no actual content, or removing material that has been pasted in from another site and infringes copyright.

• View and restore deleted pages, including images, and their history. See Atkinspedia:Viewing and restoring deleted pages by sysops for guidelines. To challenge an already made decision to delete a page, see Atkinspedia:Deletion review.

Block and unblock

• Block IP addresses, IP ranges, and user accounts, for a specific time or indefinitely.

• Unblock IP addresses, IP ranges, and user accounts.

• See Atkinspedia:Blocking policy for more information on when blocks are appropriate and when they are not. See Special:Ipblocklist for currently blocked addresses and usernames

Reverting

• Revert pages quickly. Any user (logged-in or not) can revert a page to an earlier version. Administrators have a faster, automated reversion tool to help them revert vandalism by anonymous editors. When looking at a user's contributions, a link that looks like: [rollback] – appears next to edits that are at the top of the edit history. Clicking on the link reverts to the last edit not authored by that user, with an edit summary of (Reverted edits by X to last version by Y) and marks it as a minor change.
• Do not use one-click rollback on edits that are not simple vandalism; please use manual rollback with an appropriate edit summary.

Enforcement of Arbitration Committee rulings

Admins have the authority to enforce rulings by the Arbitration Committee.

Further information: Atkinspedia:Requests for arbitration/Admin enforcement requested

Hiding vandalism from recent changes

• Admins can hide vandalism from Recent changes. To do this, add &bot=1 to the end of the URL used to access a user's contributions. For example, http://www.atkinsalltheway.com/wiki/index.php?title=Special:Contributions&target=Example&bot=1. When the rollback links on the contributions list are clicked, the revert and the original edit that you are reverting will both be hidden from the default recent changes display. (The bot marker was originally added to keep massive bot edits from flooding recent changes, hence the "bot".) This means that they will be hidden from recent changes unless you click the "bots" link to set hidebots=0. The edits are not hidden from contributions lists, page histories or watchlists. The edits remain in the database and are not removed, but they no longer flood recent changes. The aim of this feature is to reduce the annoyance factor of a flood vandal with relatively little effort. This should not be used for reverting a change you just don't like, but is meant only for simple vandalism, particularly massive flood vandalism.

Design and wording of the interface

• Admins can change the text of the interface by editing the pages in the MediaWiki namespace. This includes the text at the top of pages such as the "Special:Whatlinkshere" and the page that a blocked user will see when they try to edit a page (MediaWiki:Blockedtext).

• Admins can edit the style of the interface by changing the CSS in the monobook stylesheet at MediaWiki:Monobook.css.

Other

There are various other actions which only those with administrator privileges can perform:

• Can move category pages and other move protected pages
• Can view Special:Unwatchedpages to see pages which may be more vulnerable to vandalism
• Can view the history of deleted pages

Becoming an administrator

If you have been around for a while and you would like sysop access, add your name to Atkinspedia:Requests for adminship according to the guidelines mentioned there, and a discussion will take place by fellow editors in order to determine if there is consensus that you should become an administrator.

It is recommended that you write for Atkinspedia for a while before requesting administrator status, since other users will have to recognize you before they can agree on your promotion. Also keep in mind that each language's Atkinspedia has its own policies for administrators, which may differ somewhat.

Although multiple user accounts are allowed on Atkinspedia in certain circumstances, only one should have admin powers beyond being an editor.

Be careful, please! If you are granted access, we ask that you exercise care in using these functions, especially the ability to delete pages and their history, to delete images, and the ability to block IP addresses. You can learn about your newfound powers at the Atkinspedia:Administrators' how-to guide. You should also take a look at the pages linked from the Administrators' reading list before using any of your admin abilities.

Places where admins in particular can assist

Admin rights can be particularly helpful for working in certain areas of Atkinspedia.

• Incidents that may require admin intervention
• 3RR violations
• Intervention against vandalism
• Copyright problems
• Candidate speedy deletion pages
• Admins will also find their tools useful for RC patrolling.

Other access types

In addition to administrators, there are other types of identified users, listed here in roughly ascending order of power. Administrators lie between bots and bureaucrats on this list. See also Atkinspedia:User access levels.

IP addresses

Visitors who haven't "signed in" can still do most things, including the most important: editing articles and helping with Atkinspedia maintenance tasks.

Signed-in users

Signed-up users can do everything 'IP addresses' can do, but they can also upload files, move/rename pages, create their own user page, and start new articles; see Special:Userlogin to sign up for yourself.

Bots

The edits of users with bot status turned on do not show up in recent changes, usually only used for mass edits by bots.

Bureaucrats

Users with "bureaucrat" status can turn other users into sysops (but not remove sysop status), change usernames, and flag and unflag bots accounts. Bureaucrats are created by other bureaucrats on projects where these exist, or by stewards on those who don't yet have one. Sysoppings are recorded in Special:Log/rights or Atkinspedia:Bureaucrat log for activity prior to December 24, 2004. Sysoppings by stewards are recorded at Meta:Special:Log/rights but the few stewards who actively sysop users on Atkinspedia do so using their local bureaucrat status, making this distinction rather academic.

Stewards

Users with "steward" status can change the access of any user on any Wikimedia project. This includes granting and revoking sysop access and marking users as bots. Their actions are recorded at Special:Log/rights on meta. Requests for their assistance can be made at m:Requests for permissions. Normally, they will not perform actions that can be carried out by a local bureaucrat.

Developers

The highest degree of technical access (actually a group of levels, the difference between all but the lowest of which isn't really visible to users) is "developer", for those who can make direct changes to the MediaWiki software and the Wikimedia wiki farm and databases. These people, by and large, do not carry out administrative functions, aside from sock puppet checks and reattributing edits.

They can be contacted via the wikitech-l mailing list. See m:Developers for a list of developers and further information.

Administrator abuse

Administrators can be removed if they misuse their powers. Currently, administrators may be removed either at the request of BrianZ or by a ruling of the Arbitration Committee. At their discretion, lesser penalties may also be assessed against problematic administrators, including the restriction of their use of certain powers or placement on administrative probation. The technical ability to remove administrator status rests with stewards.

See also:

• Requests for comment/User conduct: Use of administrator privileges
• Atkinspedia:Requests for de-adminship

Dealing with grievances

If you think an administrator has acted improperly against you or another editor, you should express your concerns directly to the administrator responsible. Try to come to a resolution in an orderly and civil manner. However, if the matter is not resolved between the two parties, you can take further action according to Atkinspedia:Resolving disputes. There have been a number of alternative procedures suggested for the removal of sysop status but none of them have achieved consensus.