From SmashWiki, the Super Smash Bros. wiki
Jump to navigationJump to search
FailedPolicy.png This proposed policy or guideline has failed to gain the approval of the community, and so has not been implemented. It remains for archival purposes.

We want to see our Wiki grow, right? Well, we can help make that happen if we can ease users into our wiki as they join. Users come and go all the time, but with these guidelines, the more recent users on SmashWiki will hopefully stay and help it flourish.




Commonly here, new users tend to slip up fairly frequently a little after they join. If such users have any trouble getting used to SmashWiki, then the instructions below can possibly come into play.

Steps for the struggling user to take:[edit]

  1. If new users find themselves screwing up in terms of editing, understanding SmashWiki policies, or whatever reason, then they are eligible to make an [[SmashWiki:Requests for Upbringing|RfU]], explaining what they are struggling with.
  2. If their RfU gets enough support, then they will get "adopted", and be assigned to one of our Sysops, who will be thought of as "their sysop".
  3. After the newbie learns enough, so they'll be able to contribute on their own with less help, (this is up to their sysop), then the user is "un-adopted", or free to go, after getting used to the Wiki through their adoption.

Guidelines for the Sysops:[edit]

Each sysop will have a small group of adopted users to monitor, until they learn the ways of the Wiki. It may be best for each sysop to put a list of users they are monitoring somewhere so they'll remember. The sysop is the head of the group, and the adoptees and rollbackers in the group must obey them. If an adopted user needs attention on something, then their sysop will be responsible for giving them guidance to help them do better. When assisting the user, try to be as detailed as possible, to help them fully understand. But keep in mind: No matter how detailed the post is, the user can still ask clarifying questions, which is heavily encouraged in order to get optimum success during adoption. Also, if the user exhibits bad behavior, then the sysop has the responsibility for delivering any warnings or blocks that the new user may deserve. When giving advice, or delivering punishment to the newbies, always post in a somewhat non-strict tone to prevent retaliation on the newbie's part.

How do rollbackers fit into this?[edit]

Two of our rollbackers will be assigned to one of our participating sysops, and will share the same list of adopted users with them. The rollbackers are mainly there to check in on the adoptees when the sysop is not online at the moment, and to help the newcomers in situations that do not necessarily require sysop authority. Like the sysops, the rollbackers are responsible for delivering warnings, and must talk in a somewhat non-strict tone to minimize retaliation. Despite this position, they must obey the sysop in charge of the group. Given this, rollbackers cannot decide whether a user is free to go; only the sysop of the group can do that. However, rollbackers can still ask the sysop if the user is ready. Additionally, if the sysop of the group did not see any addressable behavior issues from the newcomers, then the group's rollbackers are responsible for reporting it to them.


To the adopted users:[edit]

  • If your sysop takes a leave of inactivity, then you are to report to another sysop, who is still active.
    • As such, if your sysop comes back before your adoption is up, then you will report back to them.
  • In addition, if you move to another sysop, then the sysop's rollbackers (and of course the sysop itself) now have authority over you, and those of your previous sysop will not, until that sysop comes back.
  • If you go inactive for more than one week before your adoption is up, then you will be removed from the group, and you must notify your former sysop on their talk page if you want to rejoin.

To the Rollbackers:[edit]

  • If one or both of you takes a leave of inactivity, then one of our free rollbackers will take your position(s) until you come back.
  • As mentioned above, if the sysop of your group goes inactive, then you no longer have authority over your group, as they are expected to move to another sysop when this happens. However, you will regain authority once your sysop comes back, and the newbies in the group return.

To the Sysops:[edit]

  • If you are for some reason not there to do something for your user(s), then other sysops have the full right to do it for you, regardless if the user is theirs or not.
    • This is why we have rollbackers in the group: to minimize this extra work for the other sysops, by doing some of the things for you while you're not online.
  • Though helping the new users in your group will be your main goal, you can still feel free to help the site in other ways too, (though keep in mind: The reason we organize groups like this is so we can determine which of our sysops and rollbackers are still free to help the Wiki after adoption groups are set up.

General Notes:[edit]

  • Unless in the rare case of a user creating a new account for non-malicious reasons, (forgetting their passwords, having the same IP as an existing account, etc.), sockpuppets may never be adopted.
  • If a user does not show enough issues in getting accustomed to the Wiki, then their RfU will not be accepted.
  • Users may not request adoption more than once.
  • In each group, the two rollbackers don't have to be rollbackers at all, but experienced users will be fine for that position too.