This ticket involves the work of enabling volunteers to configure facets of how Paste Check behaves on a per project basis.
Story
As a volunteers knowledgable about WP:COPYVIO, and experienced with reviewing/patrolling edits through the lens of this policy, I want to be able to configure facets of Paste Check to ensure that the Check is offering people feedback that is aligned with local project policy and conventions.
Facets
This section will eventually contain the facets of Paste Check's behavior that volunteers can explicitly control.
| ID | Facet | Status | Notes |
|---|---|---|---|
| 1. | Namespaces Paste Check should have the potential to activate within | Out of scope for initial rollout (T399669); we'll revsit in the context of T405127 | E.g. Drafts |
| 2. | Paste sources that should NOT cause Paste Check to activate on | ✅ Done, albeit currently difficult to do | E.g. word processors, other Wikipedia language versions, other Wikipedia articles, pages in different Wikipedia namespaces (e.g. draft/sandbox) etc. |
| 3. | People/account types Paste Check has the potential to activate for | ✅ Done via generic Check configuration | E.g. people acting in good faith (TBD how we might determine this), cumulative edit count, account state, etc. |
| 4. | Check State | ✅ Done via T404914 | E.g. Tag (tag edits that Paste Check would have been shown within were it enabled in the "Active" state), Active (show Paste Check within edit sessions initiated by people volunteers have configured the Check to be shown for) |
Reference: T330112
Thank you to @Chaotic_Enby whose comment in T387897#10602125 prompted me to create this task and to @matej_suchanek for offering ideas about how it might be useful to have Paste Check be configured on-iwki.