SmashWiki:Adoption

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.

This policy is reviving discussion in an attempt to gain concensus once more. If you want to participate, use the talk page!

SmashWiki:Adoption Policy is here to help guide newbies into our wiki, with extra support to help them learn how to be a good user, and make them more confident.

Shortcuts:

SW:ADOP

Details:

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 will come into play.

Steps for the struggling user to take:

1. If new users find themselves screwing up in terms of editing, understanding the 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:

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

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

Notes:

• To the adopted users, if your sysop takes a leave of inactivity, then you are to report to another sysop, who is still active.
  • 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 the sysop itself) now have authority over you, and those of your previous sysop will not, until that sysop comes back.
• 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.
• To the sysops, if you are for some reason not there to do something for your user(s), then other sysops have the right to do it for you, regardless if the user is theirs or not.
  • This applies to the rollbackers mentioned above: To minimize this extra work for the other sysops, the rollbackers are there to do some of the things for you while you're not online.
  • Also, if one or both of your rollbackers takes a leave of inactivity, then you must find one or two rollbackers who are not teamed with a sysop yet, have them read over this policy, and have them join your group and substitute the old ones until they come back.
• Users may not do this more than once.