Page MenuHomePhabricator

Define how volunteers will discuss and provide feedback about Tone Check
Closed, ResolvedPublic

Description

This task involves the work of defining how volunteers (likely those who are experienced with editing) can both:

  1. Provide feedback about Peacock Check when they notice it behaving in ways that they do not think align with what Wikipedia policies and guidelines prescribe
  2. Learn more about the feature itself

For Reference Check, we made it so people could tap the editcheck-references-shown tag and be taken to https://www.mediawiki.org/wiki/Edit_check/False_positives.

Although, for reasons @Trizek-WMF articulated in T353726, this approach could benefit from improvement.

Story

  1. As an occasional user, or a user discovering the Tone check tag, I want to know in a quick way what the "Tone check" tag stands for.
  2. As a user curious about how Tone check works, I want to be able to learn about Tone check in depth
  3. As a user who wants to improve the functioning of Wikipedia, I want to be able to report an issue related to Tone check, should it be
    • a bug that target the feature
    • an improvement for the model used to detect tone issues
  4. As the Tone check feature maintainer, I want to make sure that users can discover the feature and contact us.
  5. As a Mediawiki patroller, I want to limit the number of pages I have to perform reverts on

Requirements

Approach

Users should follow a unified path, that can be used for all checks:

  1. click on Check tag from a page history, diff, special:recentchanges, etc.
  2. arrive on a Help page presenting the feature page that is:
    • centralized - Mediawiki should be preferred, even if we can't prevent local communities from creating their own
    • simple - a short presentation of the feature should come first, with more details in sub-sections
      • tags used and their meaning
      • check's configuration
      • if applies, testing process
    • translatable
  3. Exit ways:
    • [if relevant] the user can go to a false-positive report page dedicated to the check
    • Suggest terms that should trigger Tone check

Using a sub-page of the main page for false positives can diminish the number of false reports.

Example for step 2: https://www.mediawiki.org/wiki/Help:Edit_check#Reference_check

Event Timeline

Aklapper renamed this task from Define how volunteers will discuss and provide feedback about Peacock Check to Define how volunteers will discuss and provide feedback about Tone Check.May 28 2025, 11:43 AM

Change #1176342 had a related patch set uploaded (by DLynch; author: DLynch):

[mediawiki/extensions/VisualEditor@master] Edit check: link the tone check help page from editcheck-tone-shown tags

https://gerrit.wikimedia.org/r/1176342

Change #1176342 merged by jenkins-bot:

[mediawiki/extensions/VisualEditor@master] Edit check: link the tone check help page from editcheck-tone-shown tags

https://gerrit.wikimedia.org/r/1176342

Minor detail:

Attached screenshot in Mediawiki doesn't depict the exact experience:

Expected:

image.png (520×704 px, 47 KB)

Observed screenshot:

image.png (643×1 px, 158 KB)

Minor detail:

Attached screenshot in Mediawiki doesn't depict the exact experience...

Hmmm. What might explain the discrepancy in copy @EAkinloose helpfully identified above?

DLynch subscribed.

There's an old screenshot from July on mw.org -- it should get updated.