Prompted by the 28 April Editing Team Community Call, and those that it spawned, this ticket involves the work of enabling volunteers to configure facets of how Tone Check behaves on a per project basis.
Story
Facets
This section will eventually contain the facets of Peacock Check's behavior that volunteers can explicitly control.
| Configurable facet | Status | Notes |
|---|---|---|
| Pages Peacock Check should never become activated on | ||
| Words/phrases/conventions Peacock Check should never consider to be non-neutral | ||
| Mode Tone Check is running in | E.g. A) Silent: tag edits the model "thinks" non-neutral language is present within without presenting Tone Check to people while they're editing or B) Active: tag edits the model "thinks" non-neutral language is present within and present Tone Check to people while they're editing | |
| Types of pages Peacock Check should never become activated on (e.g. biographies, political ideologies, active conflicts, etc.) | ✅ (T347775) | |
| Confidence/probability threshold model would need to reach in order for Peacock Check to be presented to someone | ✅ See mw:Edit_check/Configuration#Tone_check_configuration | |
| People/account types Tone Check has the potential to activate for | ✅ See Edit_check/Configuration#Generic_check_configuration | E.g. people acting in good faith (TBD how we might determine this), cumulative edit count, account state, etc. |
Reference: T330112
Thank you to @SCP-2000 who prompted me to create this task.