Difference between revisions of "User:Aichon/Sandbox/Demo8"

From The Urban Dead Wiki
Jump to navigationJump to search
Line 54: Line 54:
#Be patient. People that seem too eager for the position routinely get shot down. Especially so if they've been advised to work on one or more of the [[UDWiki:Administration/Promotions#Guidelines_for_System_Operator_Requests|Promotions page criteria]] and haven't waited long enough for real change to have occurred.
#Be patient. People that seem too eager for the position routinely get shot down. Especially so if they've been advised to work on one or more of the [[UDWiki:Administration/Promotions#Guidelines_for_System_Operator_Requests|Promotions page criteria]] and haven't waited long enough for real change to have occurred.
#Prepare to have the wiki ruined for you. Sysops, as with pretty much any other role of this sort, tend to get cynical in a hurry and lose the fun they had before. It doesn't happen to all of them, but it happens to enough that you'd be advised to consider whether or not it's worth it.
#Prepare to have the wiki ruined for you. Sysops, as with pretty much any other role of this sort, tend to get cynical in a hurry and lose the fun they had before. It doesn't happen to all of them, but it happens to enough that you'd be advised to consider whether or not it's worth it.
#Ask yourself


=Discussion Area=
=Discussion Area=

Revision as of 22:33, 26 October 2010

This guide was written in October of 2010. Policies may have changed since it was written, and it only expresses the views of one individual, so take everything it says with a grain of salt.

So, you want to be a sysop?

Honestly, chances are that you're simply mistaken and that no, you don't want to be one. What you actually want is a status badge so that other people recognize you. Or maybe you want a podium from which you can enact changes in policies. Perhaps you think you need to be a sysop do anything around here.

Most people seem to do and think things along those lines. That's fine. It's perfectly human of you. We don't hold it against anyone. In fact, we basically expect it. That doesn't make any of them good reasons to be a sysop, however. In fact, all of those are lousy reasons.

Review time

Before we talk some more about how you might become a sysop, let's first review a few important things. If you don't get these ideas, your chances or being a sysop are slim at best.

What is a sysop

If you've never read it before, the first thing you should read is the Administrative Guidelines regarding sysops. It explains, in brief, what they are, what powers they have, and how they are supposed to use those powers in practice. Read the entire thing. Mull over it. Understand it and why it says what it does. It's important, and you can be guaranteed that if you want to be a sysop, you'll be expected to be an expert on that page.

To summarize, sysops are just regular wiki users. They have access to a few more buttons at the top of their pages than normal users do, which allows them to do stuff like move pages, delete pages, protect pages from editing, and other things of that sort. They also have some special authority on administrative pages such as Move Requests, Protections, Speedy Deletions, Deletions, and Vandal Banning, to name a few, which allows them to rule on cases or act on requests made by users. Aside from the authority they have on those pages, and their special buttons that they can press, sysops are simply regular users.

To be fair, however, sysops are typically expected to be model users of the wiki, so you'll see them doing a lot of janitorial or maintenance work around the wiki, but the truth of the matter is that with 99% of that work, anyone can do it (*hint hint*).

Some of the sysops also attain the rank of Bureaucrat. We generally have two Bureaucrats at any given time, and their only additional power and responsibility is to handle promoting and demoting sysops. That's it. Nothing else.

What a sysop isn't

There seem to be a lot of misconceptions about what sysops are around here, so let's clarify a few.

  1. Sysops can't use their buttons to do whatever they want. There are specific guidelines that explain when they can and can't use their abilities, and how they must use them. Failure to do so properly gets them sent to Misconduct. For a sysop to misuse their powers is a serious matter, and past sysops have been banned for extended periods of time due to abuse of the buttons.
  2. A sysop's word is not law. Unless they are acting in an official capacity (which they almost always make very clear), whenever a sysop chimes in with their opinion in places like Developing Suggestions, Historical Groups, or elsewhere, their word carries no more weight than that of any other user.
  3. Sysops are not the only ones allowed to do most of the work. Just because you might usually see sysops doing janitorial work like cycling suggestions on Developing Suggestions or, or else updating Featured Articles each week does not mean that sysops are the only ones allowed to do those things. They just happen to be good and active users that do it to help.
  4. Sysops are not intermediaries in disputes. That's what Arbitration is for. A sysop might be able to help two users come to an agreement, but their word is no more binding than that of any other user, nor is their help to be demanded more than that of any other user.

Who gets to be a sysop?

Anyone that "the community" thinks deserves to be one and that the Bureaucrats agrees would be a good fit. If you're curious what a "good fit" is, check the Promotions page for information regarding what it takes to be a sysop. You'll notice a list of five key criteria, and while the page does say that, "If a user is highly exemplary in one criterion, a certain level of give may be extended to other criteria," in practice, if you're relying on this fact in order to get promoted, the truth of the matter is that you're probably not the exceptional type of candidate that is going to get promoted and that you should seriously look into improving in those other criteria before applying for the job.

Look through the archives on that page and see why people succeeded and why people failed. Look at the sorts of complaints and criticisms that were directed at the candidates, and see both how others reacted to them and how they addressed the comments. It should help you see what sorts of things are important or not important. You'll probably notice that time and again, people seem to overestimate their own level of qualification. A lot of users think they fit the criterion better than they do, or else they never really consulted with others to see if others thought they would be a good candidate. Had they done so, they'd have gotten a nice dose of reality prior to their nomination, which might've helped make things go better for them.

The current list of sysops is here. As you can see, there aren't many of them. In fact, generally speaking, we only have about a dozen or less at any given time. Of those, you can usually count on a few of them being inactive or infrequent contributors. Even so, for this size of community, we really only need about 3-5 active and contributing sysops in order to keep things running smoothly, though more are welcome, and we've worked with less in the past when life has happened and people have had to be inactive for a bit.

What I'm getting at is that this wiki really doesn't need' that many sysops, so it's generally only exceptional candidates that are promoted.

Looking forward

Now, I can hear you squirming in your seat, wanting to say, "That's great, but I already know all of that stuff and am a great candidate. Get to the juicy part!" I'm glad you're eager, but slow down a bit. Make sure you really understand things. If you don't, you will get called on it and it will come back to bite you.

Who really gets to be a sysop?

Okay, so while anyone could be a sysop, in practice it doesn't work that way, of course. Here's a list of unofficial criteria and additional traits that I'd say are important for any potential sysops out there.

  1. Maturity. Sysops are called on to rule in a variety of cases and routinely need to deal with drama. Being able to act as an adult when others are behaving as children is important.
  2. A demonstrated ability to deal with drama. In case you haven't noticed, this wiki has some drama on it. Sysops need to be able to wade in and set things straight without getting pulled into it.
  3. Technical expertise. Whether we like it or not, we get a LOT of questions about how to do X or Y on the wiki, and we have to fix things that break. As a model user, sysops should have a solid understanding of all of the major wikicode concepts, from headers and text formatting to tables and templates. You don't need to be an expert, but you should be a solid intermediate.
  4. Critical reasoning skills. While some cases have established precedent, it's not uncommon to see new cases around here that stretch and pull at the boundaries of what is or isn't acceptable. Any monkey can rule on a case, but a sysop should be able to form a cohesive idea in support of their side, taking into account past precedents and the differences in the case. Speaking of precedents...
  5. Understanding of past cases and history. You don't need to be a history expert on the case law of the wiki, but it's always best when a sysop comes in with a solid understanding of the major cases that have come up over the years.
  6. An established history of janitorial work. Seriously. Nothing convinces people faster that you're fit for the job than being good at contributing to the janitorial work.

Before nomination

Before you go nominating yourself (or getting your friends to nominate you), there are definitely a few things you should do that you won't find written up in many places around here.

  1. Analyze your own motivations. Figure out if you're in it because you want the status or if you really do want to help. If you really do want to help, ask yourself why you need sysop powers to help in that way. There's very little that regular users are incapable of doing.
  2. Be active and a regular contributor to janitorial work. I'll cover this in more detail in the next section, since it's probably the most important thing.
  3. Stop making mistakes. If you're making mistakes such as posting in the wrong places (especially on admin pages), doing maintenance tasks incorrectly, or suggesting ill-informed ideas in a serious manner, it tells everyone that you are not qualified.
  4. Look at your regular activities on the wiki, and determine exactly what would be different if you were a sysop. For most people, nothing at all would change if they were a sysop. If that's true for you, then maybe you shouldn't be one.
  5. Be patient. People that seem too eager for the position routinely get shot down. Especially so if they've been advised to work on one or more of the Promotions page criteria and haven't waited long enough for real change to have occurred.
  6. Prepare to have the wiki ruined for you. Sysops, as with pretty much any other role of this sort, tend to get cynical in a hurry and lose the fun they had before. It doesn't happen to all of them, but it happens to enough that you'd be advised to consider whether or not it's worth it.

Discussion Area

If you're an RC stalker (or an Aichon Sandbox stalker...creepy), feel free to add comments here, since I have the talk page redirected. This page is a WIP and is nowhere near completion. I still plan to add a list of janitorial work they could be doing, some more points to the various things I already listed, and a checklist of things they should look at before nomination.

It will not be an official document, just something I'm putting together that I can link whenever someone says they want to be a sysop. I'd find it more valuable, however, if it reflected not just my own, possibly misguided, opinions, but also the opinions of others, that way others could point to or refer to it as well. So...yeah...feel free to add your thoughts. Aichon 23:33, 26 October 2010 (BST)