@Urbanecm_WMF - Should we create subtasks for this work? I'm wondering if this task is ready for estimation.

In T426690#12054985, @KStoller-WMF wrote:

@Urbanecm_WMF - Should we create subtasks for this work? I'm wondering if this task is ready for estimation.

Thanks for the question and ping! For the first three A/Cs, I think this makes sense as is. Those values are already recognised internally, we "just" haven't added them into the form. We would need to do that (and remove the overrides we added, cf. GEReviseToneExcludedTemplates and GEReviseToneExcludedCategories).

For the fourth A/C, I would split it. The learn more link is not something Revise Tone currently supports, and while we can add it relatively easily, it is a different kind of work that would benefit from being split.

In addition to the A/Cs mentioned in this task, do note there are three other aspects that might be configureable too:

• the timestamp of the last edit (currently hardcoded to 24 hours),
• the article creation date (currently hardcoded to 90 days), and
• the threshold score for the model (currently configurable in server side config, set to 0.8 on all wikis)

Not sure if we would want to add any of those to community configuration. If so, I would probably make those a separate task.

Does this help?

Thanks, yes, that's extremely helpful! I split out the fourth A/C and the additional possible A/Cs into another task: T430380: Revise Tone Structured Task: add more advanced Community Configuration... this might also need to be broken down further, but my hope is that we can complete this task T426690 ASAP, and then consider if anything specified in T430380 is really necessary.

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

[mediawiki/extensions/GrowthExperiments@master] feat(Revise Tone): add CommunityConfiguration support

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

Change #1306919 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] feat(Revise Tone): add CommunityConfiguration support

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

I can confirm that the form is available on beta but I don't have the admin permissions(though currently seeking them) to save changes and see whether the settings affects the experience.

@KStoller-WMF you could try this out in case I don't get permissions by tomorrow or Thursday.

I had to verify on testwiki since beta doesn't have Revise Tone tasks.

I noticed that there's some caching involved between the time when settings are selected and when they apply on the "Select types of edits menu" when it comes to showing the Revise Tone task option. Overall everything seems to align to the settings.

Observation	State	CC Settings
Disabling revise tone doesn't show it as an option in the "Select types of edits menu"
Re-enabling revise tone shows it as an option in the "Select types of edits menu"
Articles in the Categories specified don't show up as revise tone tasks. This Winter Olympics 2026 article no longer shows up as a revise tone suggested edit task as per the setting.	Doesn't show as a suggested edit
Pages containing the articles specified don't show up as revise tone tasks. This Aiuto:Pagina di discussione article with the template Vedi anche no longer shows up as a revise tone suggested edit task as per the setting.	Doesn't show as a suggested edit

@KStoller-WMF you can try this out but it looks good to me on testwiki.

Waiting on resolving https://phabricator.wikimedia.org/T431625 (the task filed by me was marked as duplicate - T431623: [testwiki wmf.10] MediaWiki internal error - TypeError: array_values(): Argument #1 ($array) must be of type array, null given)

Flagging T431632: Misconfiguring Revise Tone's Community Configuration can turn off Suggested Edits for everyone as well (follow up to the task Elena shared above).