Page MenuHomePhabricator

Adapt `ReviseToneTaskTypeHandler::getSearchTerm` for production release
Closed, ResolvedPublic3 Estimated Story Points

Description

For the initial release on patch-demo we're providing the tasks directly from the loaded LocalSettings.php override. For beta, we're using the existing implementation that searches for hastemplate:peacock_inline. However, in production we will need a much more sophisticated search:

  • only show articles whose last edit is more than 24 hours old, this can be done via the newly added functionality from T403593
  • only show articles that were created at least 90 days ago, this can also be done via the functionality added in the task above
  • do not show articles that have one of the excluded templates or categories
    • ultimately, this will likely become configurable by the community, but for now we're collecting these manually from our pilot wikis and will make them available via PHP configuration
  • only show articles with the weighted tag and the respecitve threshold
    • precise name TBD, probably hasrecommendation:tone
    • the threshold filtering is being added as part of T405059
    • ultimately, the threshold will also be community-configurable, for now it will also come from PHP config: 0.8 for enwiki, 0.7 for cswiki, TBD for all other pilot wikis

Note that we will need to keep the beta search-functionality so that we can keep testing there.

Acceptance criteria:

  • By default, we search for new articles for Revise Tone in the way described above
  • On beta, we still search for new articles for Revise Tone with only hastemplate:peacock_inline

Event Timeline

Michael triaged this task as High priority.Oct 15 2025, 2:20 PM
Michael added a project: OKR-Work.
Michael moved this task from Inbox to Up Next (estimated tasks) on the Growth-Team board.

Note: estimate is about the scaffolding mainly, with the 4th criteria about wieghted tag likely needing later adjustment.

After discussing with Ambassadors, I think it’s best to avoid surfacing suggestions on newly created articles for longer than originally proposed.
Each wiki has its own process for reviewing new articles, and Ambassadors recommended that we respect those local workflows (for example, waiting until an article has passed NPP or been marked as patrolled in Flagged Revisions). To keep things simple, though, I suggest limiting suggestions to articles that are at least 90 days old for our initial tests. After 90 days, articles are typically indexed by search even if they haven’t been marked as patrolled, which makes this a reasonable threshold for assuming the article is stable and unlikely to be deleted.

Change #1198298 had a related patch set uploaded (by Michael Große; author: Michael Große):

[mediawiki/extensions/GrowthExperiments@master] feat(ReviseTone): add production search terms

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

Change #1198298 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] feat(ReviseTone): add production search terms

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

The scope of this task has been implemented. Testing can only be done in production once the actual A/B test has been launched.