User:One-Six/Policy Policy

This is way unfinished and way unofficial. Don't use it (if that's not obvious).

Policies are the set of written rules and conventions that applies to the entirety of Moegirlpedia, set by either consensus from the community (generally reflected by an official vote) or by bureaucratic action. Policies govern the action of all users of Moegirlpedia; violation of policies usually results in a formal warning or an edit block or banThe page "Moegirlpedia:Block Policy" does not exist in English Moegirlpedia yet. You may want to refer to this page on Chinese Moegirlpedia: 萌娘百科:方针#用户封禁政策. (zh:萌娘百科:方针#用户封禁政策). Due to historical and technical reasons, English Moegirlpedia has adopted and will continue to adopt many Chinese Moegirlpedia policies; however, local policies that are native to English Moegirlpedia is an important component of the policy system too – this exact policy happens to be a (hopefully) excellent specimen of such local policies.

For the purpose of English Moegirlpedia, a policy is a set of written rules and conventions, written in the "Project" namespace, ratified through a formal process as defined by the Policy Policy, and enacted by an active administrator. Policies apply to all users at all places at all times in English Moegirlpedia, with very few exceptions (such as the bureaucratic action).

In addition, Policy Policy also defines "local" and "global" policies, provides the process for the ratification and repealing of local policies, and establishes the convention for adoption, adaptation, and replacement of global policies.

Local policies

1. A local policy is a policy generated, ratified, and enacted within a local project by the local community; they apply to the local project and its community only.
2. For the purpose of English Moegirlpedia, the Local Project refers to the English Moegirlpedia itself, the Local Community refers to the community made up by all users of English Moegirlpedia, and the Local Authority refers to the authorities of English Moegirlpedia.

Changes to local policies

1. Adoption, modification, and deprecation of local policies are treated the same, referred together aschanges to local policies.
2. Changes to local policies should be based on Local Community consensus. To reflect such consensus, proposalsThe page "Moegirlpedia:Proposals" does not exist in English Moegirlpedia yet. You may want to refer to this page on Chinese Moegirlpedia: 萌娘百科:提案. (zh:萌娘百科:提案) are used as the convention to carry out such changes.
3. Changes to local policies that produce no substantial change of meaning (e.g. fixing typos or typesetting) can be carried out directly by local authorities. These kind of changes should be supervised by the Local Community.
4. Bureaucratic action and global supervision is not limited by the above policy.

Global policies

1. A global policy is a policy originally ratified by the global project of Moegirlpedia and intended for adoption by other local projects of Moegirlpedia.
2. The Global Project is a hypothetical project of Moegirlpedia that has the power to draft and ratify policies and guidelines for, make usergroup change to, provide high-level moderation for, and hold ultimate power and responsibility for all sister projects of Moegirlpedia. The Global Community refers to the community made up of all users of the Global Project, and the Global Authority refers to the authorities of the global project.
3. Until the formation of such Global Project, the English Moegrilpedia project assumes the Chinese Moegirlpedia project to be its Global Project, and all policies enacted there are considered a global policy unless the intention of not recommending a policy as a global policy is clearly announced through methods including but not limited to clauses in the said policy, written and recorded Global Community consensus, or global bureaucratic action.
4. In addition to the Global Project, the local community may, by a formal proposal, adopt a document from sources other than the Global Project as a global policy.

Adoption, localization, and adaptation

1. Adoption is the enactment of the global policy for use in English Moegirlpedia. Adoptions do not have to involve localization – non yet localized but already adopted global policies can still be enforceable in the local community. Adoptions may or may not involve adaptation to the original global policy; if an adoption involves no adaptation, it is referred to as a Identical Adoption.
2. Localization is the translation of the global policy. This translation should not in any way modify or alter the meaning of the original global policy.
3. Adaptation is the modification of the global policy for use in English Moegirlpedia; it may be made as in-line changes or amendments, as long as the addition, removal, and modification of the original text is made obvious. An adapted global policy should still be constantly updated against the original version, but the adaptations will stay as-is unless modified via the standard process for changing policies.

Strength

1. A global policy may define its global strength as one of the following:
   1. A guideline (Chinese: 指引性) global policy is not automatically enforceable in English Moegirlpedia. Whenever a guideline global policy is enacted, the local community should discuss whether to adopt or adapt such policy; if such discussions produce no result nor consensus, the guideline policy will only be treated as an official guideline and have no binding strength. A guideline policy rejected locally will not even be treated as guidelines.
   2. A standard (Chinese: 普通) global policy is automatically adopted locally when they are enacted and not subject to local rejection; however, local communities may choose to adapt it to better suit local use without any global intervention. At least one global authority should be notified when a new adaptation is passed locally to give the global authorities a chance to review the adaptation.
   3. A strict (Chinese: 强制性) global policy is automatically adopted locally when they are enacted and not subject to local rejection, and no local adaptation can be made unless reviewed and approved by at least two global administrators.
2. Strict and standard global strengths may be referred to as "mandatory".
3. A global policy may define its different sections to have different global strengths.
4. A global policy with undefined global strength is treated as having standard global strength.

Local replacement policy

If necessary, a global policy can be replaced by a local policy. The local replacement policy (an LRP) should serve the same principal function as the global policy being replaced.

A local replacement policy should be placed at

• "name of corresponding global policy/LRP/year.month of ratification" (e.g. Project:Usergroup policy/LRP/2021.4) once ratified locally
• "name of corresponding global policy" (e.g. Project:Usergroup policy) once approved (with the "/LRP/yyyy.mm" page kept as a redirect)
• "name of corresponding global policy/LRP/year.month of ratification" once replaced by a newer version or deprecated

The original corresponding global policy should be moved to "name of corresponding global policy/global" (e.g. Project:User group policy/global) once replaced by an LRP.

Adoption of LRP's

The adoption of an LRP to replace a global policy should follow one of the conventions outlined below:

1. Standard route.
   1. Local ratification. The LRP is drafted and ratified by either the local community or local authoritative action with the convention analogous to ratification of a local policy. The local ratification effort should inspect to make sure that the LRP indeed serves the same principal function as the global policy being replaced and does not conflict with other global policies.
   2. Submission for global approval. Once ratified, a discussion thread shall be submitted by a local authority to the global community, where global authorities are notified requesting their approval of the LRP. At least two global authority needs to independently inspect and approve the LRP within 30 days of the submission for approval, before which the previous adoption or adaptation of the corresponding global policy remains in effect.
      • If the local community deems an LRP for a strict global policy is necessary, at least two global administrators must independently inspect and approve the LRP before the replacement can be made.
      • For the purpose of English Moegirlpedia, an approval that originated from a global authority who drafted or co-sponsored the LRP in question does not count.
   3. Enactment. Once approved by the global authorities, the LRP goes into effect and replaces the corresponding global policy. If the approval period lapses before enough approval are gained, the previous adoption or adaptation of the corresponding global policy remains in effect, and the LRP is considered deprecated.
      • Request of approval for LRP should not be submitted within 90 days of the last request regarding the same corresponding global policy.
2. Global bureaucratic action.

Reapproval of LRP's

The reapproval of an LRP, required when either the LRP or the corresponding global policy is changed, should follow the convention outlined below:

1. Initiation. The reapproval process is initiated when one of the following events occurs:
   1. Update to corresponding global policy. The LRP must be reapproved whenever the corresponding global policy is updated. If necessary, changes to the LRP may be made and ratified through either the local community or local authoritative action with the convention analogous to changing a local policy.
      • Global authorities are not responsible for notifying changes to the global policy.
   2. Update to LRP. The LRP must be reapproved whenever it is changed. Changes to the LRP may be made and ratified at any time through either the Local Community or local authoritative action with the convention analogous to changing a local policy.
2. Submission for global reapproval. A discussion thread shall be submitted by a local authority to the Global Community, where Global Authorities are notified requesting their approval of the LRP. At least two global authority needs to independently inspect and approve the LRP within 30 days of the submission for approval, before which the last approved version of the LRP remains in effect.
3. Enactment. Once approved by the global authorities, the new version of the LRP goes into effect and replaces the last version. If the approval period lapses before enough approval are gained, the last approved version of the LRP remains in effect, and the new version of the LRP is considered deprecated.
   • Request of approval for LRP should not be submitted within 90 days of the last request regarding the same corresponding global policy unless the LRP requires reapproval due to update to corresponding global policy, in which case the cooldown time is reduced to 15 days.

Dprecation of LRP's

The Deprecation of an LRP should follow the convention outlined below:

1. Local deprecation. A locally initiated deprecation of an LRP is equivalent to a local update to the said LRP; follow the convention outlined above.
2. Out-of-date deprecation. If 90 days pass since an update to the corresponding global policy or 7 days pass since the second update to the corresponding global policy, yet the LRP is still not reapproved, the LRP goes into "limbo": any formal challenge to the LRP immediately initiates a 30-day "last-chance" period, during which the LRP remains in effect and one last attempt to get the LRP changed (if necessary) and reapproved can be made. If it cannot be approved before the "last-chance" period lapses, the LRP ceases to be in effect and is considered deprecated.
3. Global deprecation. The global community may deprecate LRP through either
   1. changing the corresponding global policy so it has the "strict" global strength; or
   2. through global bureaucratic action.

New requests for approval of LRP may be made 15 days after the deprecation of the most recent version of an LRP regarding the same corresponding global policy.

Deprecation of global policy

Whenever the original global policy is deprecated by the source community, the local community should discuss the fate of the corresponding translated or adapted policy or the LRP, until the end of which the policy in question remains in force. The local community may choose to keep the policy, upon when the former global policy will simply become a normal local policy; or, the local community can choose to deprecate the policy. If the discussion produces no result nor consensus, a former global policy is deprecated, and an LRP stays in effect as a local policy.

Deprecation of an adaptation of a global policy is equivalent to a new adaptation that removes all previous adaptations; follow the corresponding convention outlined above. If the deprecation is enacted, the global policy reverts to its original, translated but unmodified state.

Deprecation of an adopted guideline global policy is equivalent to the deprecation of a local policy; follow the corresponding convention outlined above.

Policy precedence

If policies conflict on a certain matter, the following precedence order is used, from the most powerful to the least:

1. "strict" global policy (including adaptations)
2. LRP of a "standard" global policy
3. "standard" global policy (including adaptations)
4. LRP of a "guideline" global policy
5. local policy
6. adopted "guideline" global policy (including adaptations)

Global oversight

1. Global oversight refers to the action carried out by the Global Authority to mandate modification or deprecation of one or more policies, including local policies, adapted global policies, or LRP's.
2. The Global Project retains ultimate control over English Moegirlpedia and may exercise its global oversight rights at its pleasure.
3. If required, the global community can request assistance in translating policies into the working language of the Global Project for review purposes, and the local community should comply to its best extent.
4. The initiation of global oversight should be announced by a global administrator at the suitable local public discussion page.
5. A global oversight can be made in one of two ways:
   1. Global Oversight Request for modification / deprecation. This type of global oversight requests the local community to make the necessary change(s) to the policy(ies) on its own; requirements should be made clear in the announcement to help the local community meeting it. Requests can (but do not have to) have a time limit – if the time limit lapses, the global community can carry out a Global Oversight Action; otherwise, once the global community is satisfied with the changes made, a global administrator should announce the closure of the global oversight event.
   2. Global Oversight Action for modification / deprecation. This type of global oversight directly makes the change(s) to the local policy(ies); it should either be initiated by a lapsed Global Oversight Request or by global bureaucratic action. This global oversight is immediate and instantaneous and does not have to be closed; the local community must comply with the Global Oversight Action.
6. The local community can contest a global oversight at the Global Community.
7. The exact rules as to how and when to carry out a global oversight, how to verify whether the global oversight requirements are met, and how to respond to a contest from the local community shall be drawn out by the Global Community.