STO Awakening.jpg

Hi Gamepedia users and contributors! Please complete this survey to help us learn how to better meet your needs in the future. We have one for editors and readers. This should only take about 7 minutes!

STOWiki:Policy status phases

From Star Trek Online Wiki
Jump to: navigation, search

Icon-policy.png STOWiki Policies

Policy status and phases

Admin selection policy
Category policy
Copyright policy
Deletion policy
DNP Policy
Editing policy
External links
Naming policy
Personal articles
Player character pages

Neutrality policy
Stub policy
Three revert rule
Vandalism policy
Voting policy
Writing policy
Fan fiction
Fleet pages
Items
Lore

See also:
Guideline

This page is an official policy on STOWiki.

This policy has wide acceptance among editors and is considered a standard that all users should follow.

  • Feel free to propose any changes to this policy, but please make sure that changes you make follow the official process and reflect consensus on the discussion page before you put them into practice. Any big changes need to be Adopted or Decreed to be enforced as policy.
  • See Project:Policies for an overview of STOWiki policies.
  • See Category:Policies for a list of proposed and adopted policy articles.
  • Shortcut: STOW:PSP

The life of an STOWiki policy[edit source]

These are the statuses and phases that policies at STOWiki will go through before being adopted (implemented and followed by STOWiki users) or otherwise:

Policy status and phases[edit source]

Policy pages should have a status at the top that indicates whether the policy is still a proposal, ratified, or adopted. A policy can also be recalled by users or vetoed by the Admins.

  • Policy/Proposal – The policy proposal is open for voting.
  • Ratified – The policy is in effect, but there are changes that need to be carried out or implementation details to solve before it can be fully adopted.
  • Adopted – This policy is officially accepted by the STOWiki community insofar as those who voted represent the community. It has been fully implemented.
  • Recalled – If an adopted policy gets more no votes than yes votes at some time in the future, it becomes recalled back to a status similar to proposal status, except that if the no votes exceed yes votes for some period of time (recall time), the policy becomes a candidate for deletion.
  • Vetoed – The admins can always veto a policy outright. Their rule is law, but the users can of course comment on vetoed policies to try to persuade the admins.

Vote ratios and time[edit source]

  • Ratification minimum – the winning side must have a minimum of 5 votes.
  • Ratification ratio – if the ratification minimum has been met and the yes votes exceed the no votes by 3 to 1, then the policy is has met the ratification ratio. Examples: 5:1, 6:2, 9:3, etc..
  • Ratification time – the winning side must remain winner for 1 week (7 days). However, if the ratification ratio is high (4 to 1 in favor) and the number of yes votes is high (15), 3 days is enough.
  • Recall time – also 1 week (7 days). However, if the recall ratio is high (4 to 1 against) and the number of recall votes is high (10), 3 days is enough.

The standard for a quick recall votes is lower than for adoption, since a policy that people mostly don't like is likely to cause more trouble than a policy that people do like, but some disagree with.

Decreed policies[edit source]

Some policies will be established by admin via decree without voting, unlike normal policies.

Community input is still valued in cases where an admin doesn't seem to have good reasons, so maybe another admin will revert it. Like with any other policy, you can start a vote to recall it. Or a new policy proposal to change it. But be aware that if you're e.g. proposing that STOWiki should contain exploit information, any administrator is likely to Veto it outright.

Grandfathered policies[edit source]

A grandfathered policy is a something that had been in effect and actively enforced by admins as well as the vast majority of the contributors for a long time without it having been a documented policy. This kind of de-facto standard can be documented after the fact as a grandfathered policy; usually by administrators.

Like with any other policy, you can start a vote to recall it. Or a new policy proposal to change it.

More information[edit source]

Proposition and recall[edit source]

Please see Project:Policy/Policy votes

Banners[edit source]

The following banners will appear on policy pages (proposal or otherwise) to indicate their status (and phase):

Templates[edit source]

The following templates can be used for setting up votes in discussion area of policy article:

These templates will appear, but don't need to be added manually:

Note that unlike "Vote" and "Delete" templates, there are no "/Closing" subtemplates for policies. The reasoning is that if noone cares enough to go check up on his policy without having a list of closing policy votes, perhaps it did not deserve to be a policy in the first place?

Categories[edit source]