Editing SmashWiki:How to Test Propositions

From SmashWiki, the Super Smash Bros. wiki
Jump to navigationJump to search
Warning You aren't logged in. While it's not a requirement to create an account, doing so makes it a lot easier to keep track of your edits and a lot harder to confuse you with someone else. If you edit without being logged in, your IP address will be recorded in the page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 7: Line 7:


==Testing Proposed policies:==
==Testing Proposed policies:==
<small>Note: Only ONE proposed policy/guideline can be tested at a time to prevent excessive work and confusion.</small>
Every now and then, a user, whether just a regular user, or among the higher authorities will propose a policy in hopes that it will become official. It can be supported or opposed, bashed or praised, and for the most part it works out fine. However, such debates can potentially lead to the failing of a policy that would have been just fine. A way to improve upon this is as follows...
 
Every now and then, a user, whether just a regular user, or among the higher authorities will propose a policy in hopes that it will become official. It can be supported or opposed, bashed or praised, and for the most part it works out fine. However, such debates can potentially lead to the failing of a policy that would have been remotely fine. A way to improve upon this is as follows...


#After a proposed policy is put up for discussion, users are welcome to place their initial thoughts about it on the talk page.
#After a proposed policy is put up for discussion, users are welcome to place their initial thoughts about it on the talk page.
#After sufficient time has passed, the talk page of the policy or guideline will be protected to prevent discussion, and the "testing period" will commence. The length of this time-period is usually decided by whoever proposed the policy, and should be decided based on how complicated it is, (though overly complicated ones will not be tested as it creates an obscenely large amount of work). The recommended length for a testing period is from a few days to a week, (though it can be longer if deemed necessary). Note that the policy will always reach this stage regardless of how much opposition it initially received.
#After sufficient time has passed, the talk page of the policy or guideline will be protected to prevent discussion, and the "testing period" will commence. The length of this time-period is usually decided by whoever proposed the policy, and should be decided based on how complicated it is. The recommended length for a testing period is from a few days to a week, (though it can be longer if deemed necessary). Note that the policy will always reach this stage regardless of how much opposition it initially received.
#During this time, users are encouraged to take part by acting as if the policy is official, and enforcing it as best as they can whenever the situation calls for it.
#During this time, users are encouraged to take part by acting as if the policy is official, and enforcing it as best as they can whenever the situation calls for it.
#Once the previous step is done, the talk page of the policy will be unprotected. A new section for final thoughts will be started, and discussion will resume. It is at this point in time where users can express their overall opinions, and also suggest ways to improve the proposal, as well as where the community consensus is reached, followed by the final decision, which will be based on a combinations of opinions and test results.
#After the testing-period is over, the talk page of the policy will be unprotected. A new section for final thoughts will be started, and discussion will resume. It is at this point in time where users can express their overall opinions, and also suggest ways to improve the proposal, as well as where the community consensus is reached, followed by the final decision.
#This step will only commence if the proposal fails. After making the final decision, the following 24 hours is given to undo any major changes made by temporarily implementing the policy.


==Testing Requests for User rights:==
==Testing Requests for User rights:==
<small>Note: No more than three users who are requesting rights can be tested at a time.</small>
This can also come into play when a user requests for additional rights, such as Adminship or Rollback. One thing that cannot be stressed enough is that one of the best ways to get proof of something you're trying to decide, is giving who or what you're deciding on a chance in order to get a better idea. After all, how else (other than their general reputation on a Wiki, and their knowledge on what is required for adminship) can you prove that a user is not fit for the privilege if you have not seen them with it?
This can also come into play when a user requests for additional rights, such as Adminship or Rollback. One thing that cannot be stressed enough is that one of the best ways to get proof of something you're trying to decide, is giving who or what you're deciding on a chance in order to get a better idea. After all, how else (other than their general reputation on a Wiki, and their knowledge on what is required for adminship) can you prove that a user is not fit for the privilege if you have not seen them with it?


Please note that all contributions to SmashWiki are considered to be released under the Attribution-ShareAlike 3.0 Unported license (see SmashWiki:Copyrights for details). Your changes will be visible immediately. Please enter a summary of your changes above.

Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)

Templates used on this page: