User:公的驱逐舰/Deletion process

This is an essay. 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 steward (or perhaps an patroller); also, only stewards or patrollers 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 shall be deleted, they must petition the deletion to a dedicated talk page, Project talk:Petition for deletion or Project:PfD for short. By the different cases, they shall apply first label applicable in this list to their PfD:

1. QD for speedy("quick") deletion. A set of restrictive speedy deletion criteria is established to allow quick deletion of pages that has no value; this includes pure vandalism, advertisement, stub stubs that has not been updated for a period of time, etc. Speedy deletion do not go through the discussion process; once verified by a patroller, the petition is either granted or rejected.
2. 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.
3. 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. Speedy 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. A Steward 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

Anyone may start a Petition for Deletion, provided that the target of the PfD is not subject to a PfD Exception or a Speedy-Delete Exception.

Before you start

Not all pages should 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. This recommendations do not apply to Speedy Deletions.

Before starting a petition, ask yourself:

• Is this page subject to Speedy 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)

Responsibilities, powers, and limits of the participants

General Limitations

• Only one PfD can be active for one target page. Repeated petitions are rejected.
• A PfD with the same argument as a previous PfD resolving to "keep" may be rejected.
  • The argument is that any previous argument against deletion may be used again, and deletion will still be blocked.
• The same user may not submit more than two PfD's targeting the same page within 30 days.
• The same page should not be a target for more than 5 PfD's within 90 days.
  • A page that has been deleted and then recreated, unless having the same contents as the previous one, is treated as a new page.

Non-confirmed Users

A user that have not been confirmed otherwise 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 starts. All other users should still listen to such users and consider their opinions.

Autoconfirmed Users

Any autoconfirmed users can start a PfD, participate PfD discussions, and contest a PfD.

Patrollers

Patrollers are responsible for most of the administrative PfD work. When a new PfD is added, they should verify the accuracy of the petition or nomination and open the discussion, warrant speedy deletion, or reject the deletion accordingly. Patrollers can also close discussions that have reached a consensus and warrant subsequent actions.

Patroller QD

Since patrollers can verify and close speedy deletion nominations, patrollers are indirectly granted the power to mark any page eligible for QD without involvement of any other party. If they wish to, a patroller may mark the page first before reporting on Project talk:PfD. A report should not be skipped for QD's, as other user may contest the deletion.

Stewards

Stewards have all responsibilities and powers patrollers have.

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

Suspension

Stewards are granted the power to suspend discussion for (and thus prevent the deletion of) any page in PfD. The steward 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 steward may not suspend discussions on the same page for more than once within 90 days.

Steward Action of deletion

Because a steward can delete most pages, they may prematurely close a discussion on PfD and decide to delete a page. This is called "Steward Action of deletion", a type of Administrator Action. The steward should pro

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

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 steward'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 speedy 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 of 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:

• The Main page.
• Talk:Discussion board.
• Project_Talk:Petition for Discussion.
• Any active policy pages.
• 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 be eligible for speedy deletion. These include:

• Any page that has an active PfDE.
• Maintenance categories.
• Templates that have been utilized on either over 50% of the pages, or over 2,500 pages (including redirects to this template).
• Redirects to a template, provided that the specific redirect has been utilized on either over 25% of the pages, or over 1,250 pages.

There is no real need to grant additional QD exceptions.