# How to be a Wikimedia sysop

* Action required
* The open task template
* Maintenance
* Requests for deletion
* Requests for speedy deletion
* Requests for unblock
* Copyright violations
* Proposed deletions
* Pending deletions
* Requests for custodian action
* Notices for custodians
* Templates
* Introduction to templates
* Guide to templates
* Welcome templates
* Page flag templates
* Navigation templates
* Admin templates
* Template task force
* Development
* Developing Wikiversity
* Wikiversity logos
* Service community
* Metadata
* MediaWiki Project
* MediaWiki
* Technical needs
* Reference
* Policies
* Custodians
* Custodianship (policy)
* How to be a Wikimedia sysop
* Mission
* Managing vandalism
* MediaWiki Handbook
* Parser functions
* Logs
* Bots
* Consensus
* Statistics
* Events and news
* Announcements
* Wikimania
This learning project can help you learn how to be a Wikimedia sysop (wiki administrator).
The topic of "how to be a Wikimedia sysop" is one which engenders a great deal of emotion among some people, so please be patient while this project develops, or if you need to blow off steam, use the talk page. Thank you!

## Introduction
### Purpose of this course

Newcomers to Wikimedia Foundation wiki projects are often filled with enthusiasm at the start and often feel they would like to contribute on the administrative side as well as on the content creation side. The openness of Wikimedia projects is inviting to newcomers. Back in the early days of Wikipedia, rules and conventions were fewer and the paths to full involvement shorter and easier. As time has gone by, Wikipedia and some of its sister projects have become awesome monoliths of bureaucracy (at least to the outside eye) and it is much more difficult to become fully and deeply involved.
This development is really nothing different from what one sees in other fields of knowledge and ability. In the ancient days of computing, most programmers were self-taught and it didn't really take a lot to become famous. These days you need several years of carefully structured training even to get a modest income. Like it or not, with Wikipedia at over 4 million articles and the #6 internet website by traffic, the days of training for Wikipedia are here. All other fields of special abilities and knowledge are like this, beginning with autodidacts and maturing with educational programmes in which experience is accumulated and passed on to maximize the efficiency and quality of each subsequent generation.
The most obvious side of training is, of course, training editors to be editors: e.g., how to
* make your first edit
* create bulleted and numbered lists
* sign your name
* use a template, etc.
* For more info, see this page
Wikiversity aims to develop an extensive range of tutorials for wiki participants, and will hopefully become a place where other Wikimedia Foundation projects send their new participants.
Giving people administrative tools can be a good thing. People may feel like their fellow participants trust and respect them. The added responsibility may give them a sense of pride. They may also feel they have a greater stake in the success of a wiki which can encourage them to become more involved, stay longer, and contribute more. Being a good administrator can also be incredibly difficult. Peers can often be highly critical of the decisions made. Peers often feel that they would have done a better job or made better decisions. This can cause administrators to feel alienated from their peers. Keeping yourself enthusiastic, optimistic, and uncritical can be extremely difficult to achieve, even on small wikis.

### Status of this course

This course is optional! Whether this course will contribute towards your personal goals is entirely up to you. This course does not confer or guarantee responsibilities - but it may transfer ability. Nobody should feel that they have to take this course in order to obtain sysop tools or other tools on any Wikimedia project. Nor should you think that taking this course somehow guarantees that your fellow peers will support you receiving sysop tools.

### Constructive criticism of this learning concept

There is a school of thought at Wikimedia which tries hard to retain the original amateurishness of sysop status. People who follow this school of thought may make comments such as "...is no big deal" (implying anyone from off the street can do it) and will find it hard to conceive of or accept how anyone could train sysops. There are perhaps other schools of thought with opinions about sysops. As a part of this course, representatives of these schools should be given an opportunity to express their viewpoints.

### What makes a good sysop?

This is a rough sketch of the general areas which a sysop should try to cover, one way or the other.

#### Human resources

People matter. People are a greater asset than a wiki's content, especially in a collaborative learning environment like Wikiversity:
* Teachers create learning materials.
* Researchers present new ideas and information.
* Editors improve the quality of materials.
* Learners provide useful feedback.
You don't have to be good with people to be a sysop, but if you aren't, please try your best to stay away from people-related tasks. People-related tasks include:
* Orientating and having sympathy with newcomers
* Retaining, supporting and encouraging established participants
* Feeling out and developing consensus and expressing where you think consensus lies
* Defusing heated conflict between participants
Staying away from people related tasks is often easier said then done. While on many wiki's having sysop tools does not give any special editorial control over content, this fact is frequently misunderstood by other editors. It is easy in the course of an ordinary disagreement about the content of a resource for users without sysop status to feel that a sysop is pulling rank. If you ever feel this is the case it is best to remind the other editors involved that you have no special privileges. This can require a lot of maturity from the sysop in particularly difficult disagreements.

#### Technical abilities

Knowing how the MediaWiki software works and being a good editor. Sysops don't have to be techies, but if you aren't, try to recognize this and ask those who know better (make sure you know who the technically good people are). Nonetheless, you should probably master the most basic technical tasks, such as those associated with recent changes patrolling, and make sure your core editing skills are high. Techie tasks include:
* Knowing how the sysop tools work:
** Rollback: Be careful. Let's say that a user makes four edits to one page, but only the last edit is vandalism. If you use rollback it will remove all four edits by that user back to the last version edited by someone else. In this case you would want to use Undo instead. The other occasionally tricky thing with rollback is that you're not really sure what the version you're returning to looks like, and on rare occasions you might revert back to a version that was vandalized already by another user (or even the same user if they have a shifting IP). That's more often a problem on Wikipedia than Wikiversity though... Wikipedia has a lot more vandals.
** Deleting
** Blocking
** Protecting: There are certain templates that are targets of vandals, for instance inserting a crude message or image in {{welcome}} Take a look at the log edit summary to get an idea of how it has been used in the past. A short protection might be used if there is an edit war, but you would need to think about that one carefully. Would it really cool off a heated argument or make it worse? Protection may also have been used a couple times to prevent recreating pages that were deleted as being outside the scope of the wiki. Advertising, for example. Also, click on the Protect tab and read the comments in the drop down box which are some of the common reasons. Notice also that there are options like Block New and Unregistered Users from editing which can be used to prevent vandalism, while allowing existing users to continue working on the page. You can also specify a short duration that is longer than the attention span of a vandal.
** Revision deletion: Page edit histories and action logs can have specific entries deleted. This reduces transparency and is only to be used in very specific situations, such as serious libel, highly offensive material, identity outing etc.
* Templates
* Style sheets (the CSS things) (sitewide ones are handled by Interface administrators)
* Bots (a rare skill)
* System messages

#### Organisational skills

* Categorisation
* Tagging
* Archiving
* and other organisational issues

#### Hybrid skills

Being both a people person and a techie is a difficult thing. If you can combine them, it's good.
* Advising on the use of the wiki
* Recognizing the subtle differences between good and bad faith edits and knowing how to deal with this in a manner which strengthens rather than weakens community

#### Problem solving skills

* Communication options
* Key policies
* Good practices
* Not so good practices
* Possible actions:
** Administrative templates
** Undoing
** Reverting / rollback
** Deleting
** Protecting
** Blocking
** Oversight

#### Fun and enthusiasm

    All work and no play makes Jack a dull boy. -- proverb
You might be wondering, what does having fun and enthusiasm have to do with being a good sysop? Sysops are volunteers, and like any volunteer, sysops need to stay motivated. Remember to have fun. Having fun is a good way for sysops to stay motivated and enthusiastic about a wiki. If a sysop works too hard the work can become dull and boring.

## Content

The general idea behind this course is that it should be an active teaching and learning process with real interaction between experienced and inexperienced users. Within their time availability, the initial concept is that tutors will involve students in regular learning and maintenance activities and provide them with feedback on their performance. Learn more...

## People involved
### Current tutors

It is proposed to have a clear division among participants between tutors and students, where tutors are experienced sysops and bureaucrats from Mediawiki (and especially Wikimedia) projects. It is further proposed that there should be no one-to-one relationship of tutor to student - a team-teaching concept is preferred. This is different from mentorship of custodian candidates, which is a one-to-one thing. In team-teaching, all tutors are collectively involved with all students.
* SB_Johnny
* Jtneill
* mikeu

### Current students

New students can add themselves here. Use a *-list.
* Add your name here with --~~~~

### Graduated students

Credits and externally recognized certificates are not awarded for this course, but for those who have successfully participated, the tutors will, in general, be willing to support a subsequent admin or custodian request, citing the student's successful participation. Please do not add yourself here - you will be added by a tutor in the course of time.
* User:Jtneill has been certified by me as having successfully participated in this project. User:Jtneill is further recommended to become a tutor on this project. --McCormack 08:09, 9 May 2008 (UTC)
* User:Gbaor did a great job as well. --McCormack 06:51, 28 August 2008 (UTC)