Guild Wars Wiki:Policy

{| cellpadding="0" cellspacing="0" style="width: 100%; border: 2px solid #C49277;"
 * colspan="2" style="background: #E7B79F; border-bottom: 1px solid #C49277; padding: 2px; text-align: center;" |
 * colspan="2" style="background: #E7B79F; border-bottom: 1px solid #C49277; padding: 2px; text-align: center;" |

 Policy

The portal to all Guild Wars Wiki policy-related pages. Policy proposals or revisions are announced on this page, together with an updates on existing policy discussions.
 * style="padding: 8px 8px 0px 8px; background: #F3E4DE;" |
 * style="padding: 8px 8px 0px 8px; background: #F3E4DE;" |

Content policies
These policy pages clarify the type of content that should be added to the wiki:


 * Content retention defines our content scope.
 * See our stance on copyrighted content.
 * Image resources are under a more specific policy.
 * Review our deletion policy on the process and criteria for deletion.
 * User pages are governed by a separate policy.
 * All guild pages are subject to the guild pages policy.
 * We keep notable fansites listed on a single page.
 * Articles about common builds are permitted on this wiki.

Editing policies
These policies encompass content contributions:
 * Please sign your comments on article talk pages with non-disruptive signatures.
 * Do not revert more than once before a consensus is reached.

Conflict policies
These policies deal with appropriate user behavior or response:
 * When a disagreement occurs, there must be no personal attacks. Discuss the edit, not the editor.
 * The final way of solving user conflicts, the Arbitration Committee, is governed by the Arbitration policy.

Administrative policies
These are policies that govern administrators (sysops and bureaucrats) and administrative duties:
 * See what adminship means and what different administrator categories do.
 * Elections are used to determine new bureaucrats.
 * Requests for adminship outlines the process through which sysop status is granted and revoked.

Other policies

 * Use the requests for technical administration page to discuss useful additions to the wiki software.
 * Guidelines fulfill the role of establishing conventions.
 * Bot accounts are limited by the bots policy.

Changing existing policies
Accepted policies must never be modified arbitrarily or immediately. A policy proposal must first be made and discussed. Start by clearly explaining or describing the proposed change on the talk page of the policy in question. Create a subpage for drafting if necessary. Be sure to properly explain your reasons.

Proceed to modify the section below and add a link to your proposed policy change, including a brief summary of the proposed change. Please sign and date the entry. Be sure to keep the entry updated should there be major changes to the proposal.

Consensus must be reached before any proposed change can be adopted. If consensus is not achieved, the change proposal must be rejected. It is important to note that majority support is not an indication of consensus.

Recently implemented changes

 * Guild_Wars_Wiki:Copyrighted_content/Draft-02-15-2010 07:02, 17 February 2010 (UTC)
 * Guild_Wars_Wiki_talk:Guild_pages--Lensor ( talk ) 09:41, 5 November 2009 (UTC)
 * Guild Wars Wiki talk:Deletion policy 16:11, 12 October 2009 (UTC)
 * Guild_Wars_Wiki_talk:Adminship 11:17, 10 August 2009 (UTC)

Recently failed (or inactive) policy changes

 * Guild Wars Wiki:Policy/Draft20091119 04:48, 20 November 2009 (UTC)

Proposing new policies
Proposing a new policy for discussion is similar to proposing a policy change. Start by creating a new article in the "Guild Wars Wiki" namespace that details your new policy. Be sure to name the new article properly and similar to existing policies. Do not categorize it into Category:Policies but make use of policy instead. If necessary, consider using the draft status to indicate that a new proposal is still in a drafting stage.

Once the new proposed policy page is ready, add an entry to the section below and include a brief summary of why the policy would be helpful. Please also sign and date the entry. Be sure to keep the entry updated should there be major changes to the proposal.

Consensus must be reached (via discussions on the talk page) before any proposed policy can be adopted. If consensus is not achieved, the proposed policy must be rejected. It is important to note that majority support is not an indication of consensus.

If the proposal was a success, add it to the list of policies above and change the status of policy. Remember to move the proposal entry below to the top of the section for recently accepted policies and sign it.

If the proposal failed, move the proposal entry below to the top of the section for recently failed policies and sign it. Also, change the status of the policy template to rejected instead. Failed policy proposals should not be brought up again for at least another month or two.

In any case, once the proposal is concluded, remove it from the list of policies being proposed. If the policy proposal failed, add it to the top of the recently failed list, along with the date. Failed policy proposals should not be re-proposed for some time.