Deletion Self-responsibility: 16 Yays - 11 Nays, 59%, motion carried
Slug Reservation: 27 Yays, 100%, motion carried
Staff can summarily delete works posted in eligible slug [etc]: 12 Yays - 14 Nays - 1 Abstain, 46%, motion denied

I'm not a fan of summarily deleting a work posted in an eligible slug. We should move it or ask the author to move it.

There are legitimate reasons authors may not be able to delete words without staff help.

I don't think summarily deletion is fair given that creating a placeholder is something staff may or may not do - I'd favor moving to another slot instead to preserve comments snd votes but that's not what we're voting for here.

It's not enough, IMO, but requiring users to carry out their own deletions is better than nothing.

For reasons as specified on the most recent discussion.

After certain legal issues were brought up WRT banned users, I do think we should allow for at least staff deletion and (potenal) reposting of works without atribution by banned users upon request.

Deletion Self-responsibility

Staff will no longer execute voluntary deletion requests. Authors will be wholly responsible for removing their own works, as well as maintaining their own deletion permissions. They can request for articles to be unlocked to this purpose, but staff is not obligated to intervene further on the author's behalf.

The following paragraphs on Deletions Guide will be removed:

If an author should request their material be removed, and be able to prove authorship beyond a reasonable doubt, these requests are granted. Authors may also request deletion of all their work to be done by staff. This will likely require a basic explanation of why, and may not be immediate, but generally speaking the wiki staff will acquiesce to such requests.
If circumstances imply that a request for deletion is being made during a time of distress, or there is evidence of malice or spite on the part of the user, requests for self-deletion may be delayed or denied.

Failed self-deletions (deleted:) will still be considered a technical error and summarily deleted.

Slug Reservation ability

Staff will have the ability to reserve slugs by creating placeholder pages. The content of the placeholder created here should be one (or more, if applicable) of the following:

• A disclaimer regarding the circumstance of removal (relevant discussion: Deleting Bright's articles)
• A redirect
• An idea summary of the work previously held at this slot. This will be tagged with rewritable and considered an open entry on Curations' docket
• Navigation-specific functions (e.g. disambiguation, See also)

Eligible-for-reserving slugs exists under the following conditions:

• SCP slots
  • Staff may reserve slots in existing Series that were recently vacated due to non-negative-vote deletion and were at least one of the following:
    • older than 2 years old,
    • was a prize of a Contest (such as Kcon).
  • Contest Staff (or equivalent) may reserve any slots in unopened Series.
• Non-SCP slugs
  • Staff may reserve slugs that were recently vacated due to non-negative-vote deletion, and were older than 2 years old.
• The Technical Team can reserve any slug indefinitely for technical function or mitigation of technical issues (see Poisoned Slots)

Staff may move or summarily delete any articles posted to an eligible vacant slug up until 7 days after the initial vacation. If no placeholders are created within that timeframe, staff forfeits reservation rights to it until the next time it is vacated due to non-negative-vote deletion. Eligible slugs can also be voluntarily forfeited sooner than 7 days, at staff's discretion.

Placeholders may only exist indefinitely with a passing Staff vote (excepting Technical Team's purview). Otherwise, they can only exist for up to 6 months, after which they must be vacated, and the slugs considered ineligible for further reservation (until the next time it is vacated due to non-negative-vote deletion.) Fiats may be used to extend the duration, but for no longer than a year.

This is not meant to be used to perpetually occupy a slug, but rather to resolve the underlying situation in under 6 months where possible. Seek other methods to deprecate the placeholders naturally, such as the Slot Goblin contest.

Integration with Unlisting Policy

Slots vacated and reserved by use of the unlisting policy is not subject to the 6-month time limit.

Voting Template:

||~ ||~ YEA ||~ NAY||
||Deletion Self-responsibility|| X || X ||
||Slug Reservation|| X || X ||
||[If Slug Reservation is Yea]Staff can summarily delete works posted in eligible slug within the 7-day timeframe|| X || X ||