User:公的驱逐舰/Deletion process

This is an essay draft. It is not an official policy of Moegirlpedia.

This page outlines a proposal for a content deletion process.

Overview

Deletion is revertible, but it is cumbersome and can only be done by an administrator (or perhaps an patrol); also, only administrators or patrols can delete pages anyway. As such, Moegirlpedia requires all deletion be submitted through a petition process to allow verification can discussion (if applicable).

When a Moegirlpedia user decide that a page shall be deleted, they must petition for deletion to a dedicated talk page, Project talk:Petition for deletion or Project:PfD for short. By the different cases, they shall first apply a label applicable in this list to their PfD:

1. QD for Quick deletion. A set of restrictive quick deletion criteria is established to allow quick deletion of pages and files that have no value; this includes files replaced and no longer used, pure vandalism, advertisement, stub stubs that has not been updated for a period of time, etc. Quick deletion do not go through the discussion process; once verified by a patrol, the petition is either granted or rejected (and subsequently closed).
2. FD for File deletion.
3. UD for User page deletion. According to Moegirlpedia policies, user pages are subject to less restrictions and should use a different deletion criteria. Because user pages are the only pages on MGP that has owners, a PfD for user page must attempt co contact the owning user; failure to do so result in a rejection of deletion. In general, a discussion will open and decide the result of the PfD (if it is verified and accepted), and only a consensus can result in a deletion. Lack of consensus and non-activity result in premature closure of a PfD.
4. RD for Regular deletion. Any PfD not fitting the above criteria is a regular deletion, subject to general deletion policy. A discussion will open and decide the result of the PfD (if it is verified and accepted), and only a consensus can result in a deletion. Lack of consensus and non-activity result in premature closure of a PfD.

There are three ways for a decision of deletion to happen:

1. Quick deletion. The criteria is met and no discussion nor consensus is needed.
2. Consensus. The discussing party have come to the resolution that the page nominated meets the deletion criteria and should be deleted.
3. Administrator action. An administrator or Bureaucrat may prematurely close the discussion and decide to delete the page. Administrator action should be used sparingly and with caution.

Starting a petition

Any autoconfirmed user whose rights are not otherwise suspended or limited may start a Petition for Deletion, provided that the target of the PfD is not:

1. Already in the deletion queue,
2. subject to a PfD Exception, or
3. currently being petitioned for deletion.

Comment: Before you start

Not all pages can be submitted for deletion.

• The PfD Exceptions are part of the policy and cannot be circumvented.

In some cases, we recommend against deletion.

• A page with a {{Work in progress}} template should not be nominated for deletion (assuming that someone is actively fixing issues on that page) until the WIP expires; a stub stub should not be nominated for deletion within 7 days of its creation. These recommendations do not apply to Quick Deletions.

Before starting a petition, ask yourself:

• Is this page subject to Quick Deletion?
• If it is not, is this a work-in-progress?
• If it is not, why is it worth deleted?
• Can I help improving this page so it will not be deleted?
• Can I notify someone else (e.g. the creator or main contributor of the page) to improve this page so it will not be deleted?

Remember that you and other editors can always edit these pages so that its better quality prevents a PfD. When possible, consider fixing over deleting.

Submit a PfD

(omitted)

Discussions

1. When a PfD is accepted by a patrol, the discussion opens. People may start discussion before a PfD is verified, but this is not recommended as the patrol may reject the PfD.
2. The discussion should involve editors that have worked on the page. In practice, the creator of the target must be notified of the PfD; the petitioner should attempt reaching important contributors to the target (if they are not the creator).
3. Use discussion templates wisely.

Voting

1. Voting is not a recommended method to resolve PfD, but it may be used as a last-resort to stop heated or long-outstanding discussions.
2. A vote should be started by a patrol or an administrator. It shall last 7 days.
   • When all eligible voting party has voted, the vote may be quickly closed within 24 hours.
3. The voting party should include all autoconfirmed users that have participated in the PfD in question; those that have not participated before a vote is announced may not join that vote.
4. Any patrols or administrators, unless needing to recuse themselves for involvement in previous PfD's, may opt into the voting party after the vote is announced. If they don't opt in, they are not counted as an eligible voting party.
5. A vote should consist of two possible choices only; any other choice are considered invalid. See below for two examples:
   • "Do you wish to keep this page? Use {{keep}} or {{delete}} to cast your vote."
   • "What do you want to happen: (✕)Delete or (→)Move to userpage subpage?"
6. The vote pass with simple majority, unless otherwise required by the voting party.
   • Try not to vote on how to vote.
7. The vote serves as consensus only when the turnout is at or over 50% of the eligible voting party.

Possible Results

A discussion can be closed when

1. the parties resolve the discussion through consensus;
2. the discussion is abandoned, i.e. no resolution was reached and there were no new discussion entries for at least 15 days;
3. the discussion did not come to a consensus after 30 days; or
4. an administrator suspend the discussion.

The resolution of a discussion is reached via consensus, vote, or SAD/BAD. It may be:

1. Delete.
   1. SAD or BAD.
2. Keep.
3. Merge (to another encyclopedia page).
4. Move (to another location within the wiki, such as an userpage subpage).
5. Move to another language.
6. Move to Moegirl Archives.

Responsibilities, powers, and limitations of the participants

General Limitations

1. Only one PfD can be active for one target page. Repeated petitions are rejected.
2. The same user may not submit more than two PfD's targeting the same page within 30 days.
3. The same page should not be a target for more than 5 PfD's within 90 days.
   1. A page that has been deleted and then recreated, unless having largely the same contents as the previous one, is treated as a new page.
   2. A page that has been deleted and then restored is treated as the same page.

Non-confirmed Users

A user that have not been auto- or otherwise confirmed cannot start or contest a PfD. They can still participate in discussions, but their disagreement will not prevent the establishment of a consensus, and they cannot vote if a vote is used to resolve a discussion. These users' comment and vote should not be deleted (they should be crossed out instead), and all other users should still consider these users' opinions.

Autoconfirmed Users

Any autoconfirmed users can

1. start a PfD,
2. participate PfD discussions,
3. participate in PfD votes, and
4. contest a PfD.

Patrols

Patrols are responsible for most of the administrative PfD work.

1. When a new PfD is added, they should verify the accuracy of the petition or nomination and open the discussion, warrant quick deletion, or reject the deletion accordingly.
   1. If a PfD is rejected, the patrol must cite a reason for rejection. This is usually a term from this policy. Necessary links should also be provided.
2. If the target page have previous PfD discussions, patrollers need to link to them. If the nomination has mentioned previous PfD discussions, patrollers should check their accuracy.
3. patrols can also close discussions that have reached a consensus and warrant subsequent actions.

Patrol QD

Since patrols can nominate, verify and close quick deletions, patrols are indirectly granted the power to mark any page eligible for QD without involvement of any other party. If they wish to, a patrol may report a QD to Project:PfD after marking it.

Administrators

Administrators have all responsibilities and powers patrol have.

1. In general, administrators should be the one closing discussions and providing closing comments.

Suspension

Administrators are granted the power to suspend discussion for (and thus prevent the deletion of) any page in PfD. The administrator should provide some argument as to why should the discussion be suspended.

The community can always open a new PfD. Note that the limits on opening PfDs still apply.

The same administrator may not suspend discussions on the same page for more than once within 90 days.

Administrator Action for Deletion

Because an administrator can delete most pages, they may prematurely close a discussion on PfD and decide to delete a page. This is called "Administrator Action for Deletion", a type of Administrator Action. The administrator should provide adequate reason for executing SAD.

Like any other deletions, SAD may be contested. The administrator that executed SAD should not participate in the contest.

Bureaucrats

Bureaucrats have all responsibilities and powers administrators have.

Deletion

If a decision for deletion has been reached, the target page can either go into a deletion queue or be urgently deleted. Unless policy permit, all page should be put into a deletion queue; the page in the queue shall be deleted in batch as administrator's time permit.

In general, an allowable scheme is to prevent adding any new entries to the queue on the day batch deletion happens.

Urgent deletion

Pages subject to urgent deletion will be deleted immediately (or at the very least as soon as possible) after a decision for deletion is made. Some quick deletion criteria warrant urgent deletion (such as violation of law, privacy-related matter, etc.); almost no other deletion criteria allows for UD. A bureaucrat may subject UD to any administrator action for deletion they have taken. This action should be taken sparingly and with caution.

PfD Exceptions

General Exceptions

Some pages will never be subject to a PfD (including administrator action). These include:

1. The Main page.
2. Talk:Discussion board.
3. Project_Talk:Petition for Deletion.
4. Any active policy pages.
5. Any redirect to an active policy, outlined in that policy.

Granting of PfD GE

Any active policies may invoke the PfD policy to grant PfD GE to any number of pages.

• Essentially, another policy may amend the above PfD GE list and grant PfD GE. If the PfD policy was never ratified or withdrawn, all granted PfD GE's loose their power.

QD Exceptions

Some pages will never (and should never) be eligible for quick deletion. These include:

1. Any page that has an active PfD GE.
2. Maintenance categories.
3. Templates that have been utilized on either over 20% of the pages, or over 1,000 pages (including redirects to this template).
4. Redirects to a template, provided that the specific redirect has been utilized on either over 10% of the pages, or over 500 pages.

There is no current interest in granting additional QD exceptions.