Skip to content

MODERATION.md

Latest commit

 

History

History
51 lines (35 loc) · 2.87 KB

MODERATION.md

File metadata and controls

51 lines (35 loc) · 2.87 KB
Raw

Plugin Moderation & Removal Policy

Guidelines and procedures for registry maintainers and plugin moderators.

Moderator Commands

Moderators manage plugin status by commenting commands on the plugin's tracking issue:

  • /broken: Flag the plugin as non-functional or incompatible with current DMS.
  • /working: Clear the broken flag after fixes are verified.
  • /unmaintained: Flag the plugin as abandoned by its upstream author.
  • /deprecated: Flag the plugin as deprecated or superseded.
  • /review: Mark the plugin as verified by a moderator.
  • /unreview: Remove the reviewed mark.
  • /similar #<issue>: Link related plugins (use /unsimilar #<issue> to unlink).

Plugin authors may also use /unmaintained or /deprecated on their own tracking issues.

Plugin Removal Policy

Purging a plugin removes its entry from the registry, breaking existing installations. Deprecation is always preferred over deletion.

Core Principles

  • Deprecation First: Flag tracking issues with /deprecated or /unmaintained instead of deleting the registry entry.
  • Verification & Grace Period: Non-emergency removals require verification and cooldown before purging (3 consecutive daily strikes for dead repositories; 60-day adoption window for obsolete plugins).
  • Adoption First: If an unmaintained plugin remains useful, priority is given to updating the repository pointer to an active community fork instead of purging.

Purge Tiers

Tier Reason Criteria Verification / Cooldown Action
1 Emergency Malware, security exploits, unauthorized exfiltration, or legal/DMCA takedowns None Immediate deletion by maintainers
2 Dead Upstream Repo deleted or returns 404/410/451 across 3 consecutive daily automated check runs 3 daily strikes Automated removal PR opened for moderator review; merged or closed manually (never auto-merged)
3 Obsolete / Broken Flagged /broken or /unmaintained > 6 months with no upstream activity, or superseded by built-in DMS features 60 days Purge only after adoption period expires
4 Author Request Verified request from original author 14–30 days Advance notice before removal; community may fork and retain entry

Process for Obsolete Plugins (Tier 3)

  1. Deprecate (Day 0): Flag tracking issue with /deprecated or /unmaintained.
  2. Adoption Window (Days 0–60): Label issue help wanted or adoption-needed. Community members may adopt by submitting a PR updating repo to an active fork.
  3. Purge (Day 60+): If unadopted, run the purge tool to remove the plugin files and update registry data: 
    python3 script/purge_plugin.py <plugin_id>

Restoration Policy

A purged plugin may be restored at any time via PR if an active, compatible repository is provided and verified.