Description

Collaboration Team had previously intended to release the RC Filter Improvements only to ORES wikis. But after discussing the matter, we intend instead to offer these improvements to all wikis. I'm creating this ticket so that we can air this plan fully with interested parties. Once we've got general approval, I'll nail down any details on the various tickets that need updating (most notably, T144457, which describes the current opt-in options and T150059, which discussed changes to other Preferences.)

Here are the main points of the new plan:

Enable ORES by default

See T158225: Enable the ORES good faith and damaging UI by default, on wikis that have these ORES models available (instead of behind a Beta Feature)

"New filters for edit review" beta option

The "New filters for edit review" beta option will continue to work more or less as described in T144457.

Selecting this option turns on the new filtering interface for RC Page ( and then for other review pages as they come on line).
Existing ORES beta users will automatically be opted in to the "New filters" beta.
On ORES wikis, "New filters" users will get the ORES filters as part of the new interface package automatically.
On non-ORES wikis, "New filters" users will get the non-ORES filters only. At such time as ORES is enabled on a given wiki, the new ORES filters will automatically be displayed for all "New filters" users on the pages for which the new filters have been implemented.
- (On these newly minted ORES wikis, I don't think we'll want to offer "classic ORES" on the non-RC Page review pages—along with the related preferences. Since we don't plan to support this technology, it makes no sense to spread it and then just remove it. Though this wasn't something the team discussed. We could simply implement the plan on the new wikis as described above for the existing ORES wikis.)
The release plan will still go in phases. 1) pt.wiki, 2) the rest of the ORES wikis (order not decided), 3) all other wikis?

@Halfak and @Jdforrester-WMF, do you see anything you want to bring up? Refinements, objections... @Trizek-WMF, I think you missed the meeting where we discussed this, so please have a look.

Release

Group #1

Portuguese Wikipedia T156157
Polish Wikipedia T158042

Group #2: wikis with ORES enabled, excluding en.wp T158332
Group #3 T158333

English Wikipedia
non-ORES wikis

Group #4: remaining wikis with ORES enabled

Everywhere else T158335

	Subject	Repo	Branch	Lines +/-
	Enable RCFilters beta feature on all wikis except wikidatawiki, nlwiki, cswiki, etwiki and hewiki	operations/mediawiki-config	master	+12 -16

Status	Assigned	Task
Duplicate	Qgil	T125545 Phabricator Q&A session for Community Liaisons
Resolved	Qgil	T116025 Goal: Align Community Liaison and Developer Relations project management practices
Resolved	Qgil	T119387 Community Liaison and Developer Relation quarterly goals for January - March 2016
Declined	None	T121500 Unify product documentation for users to make it easier to share, translate and edit
Resolved	Johan	T128790 Translation strategy – act and refine
Resolved	Trizek-WMF	T129088 Create an easy to maintain glossary to facilitate documentation translation (help pages and technical documentation)
Resolved	• jmatazzoni	T145875 Create and maintain Edit Review Improvements documentation
Resolved	• DannyH	T171977 Annual Plan 2017-2018, Audiences 5: Increase current editor retention and engagement
Resolved	• DannyH	T171981 Annual Plan 2017-2018, Audiences 5, Goal 2: Give better ways to monitor contributions
Resolved	• jmatazzoni	T157642 Graduate New Filters UX out of beta on Recent Changes on ALL wikis
Resolved	• jmatazzoni	T144458 Launch ERI RC page features as a Beta Feature to all wikis
Resolved	• jmatazzoni	T150715 Release strategy for RC page improvements: what wikis get the new features when?
Resolved	Trizek-WMF	T146669 Create dedicated pages for ERI Recent Changes Beta project
Resolved	• jmatazzoni	T141449 Define Edit Review Improvements glossary
Resolved	• jmatazzoni	T145157 Research current "new user" definitions and consider whether we need a different name for the ReviewStream and RC page “new user” flag / filter
Resolved	• jmatazzoni	T151477 Improve Filters for Special:Recent Changes documentation page on mediawiki.org
Resolved	Trizek-WMF	T154889 Mark Edit Review Improvements glossary for translation
Resolved	Pginer-WMF	T147632 Prototype an improved version of Recent Change designs
Resolved	• jmatazzoni	T146333 Research how to present ORES scores to users in a way that is understandable and meets their reviewing goals
Resolved	• Catrope	T150959 Integrate a feedback page link in Recent Changes Beta filters
Resolved	Pginer-WMF	T160063 Explore ways to represent visually the ORES-related filters and associated tradeoffs
Resolved	• jmatazzoni	T161015 Add screenshots to the help pages for Recent Changes Filters Beta project
Open	None	T142782 Explore process for turning on RCPatrol for English and other relevant wikis
Resolved	Trizek-WMF	T158004 Release RC Page filtering to non-ORES wikis
Resolved	Trizek-WMF	T158225 Enable the ORES good faith and damaging UI by default, on wikis that have these ORES models available (instead of behind a Beta Feature)
Resolved	Trizek-WMF	T159223 Inform communities about the release of the ORES good faith and damaging UI by default
Resolved	Trizek-WMF	T146972 Announce and follow up with communities about the New Filters for Recent changes Beta deployment
Resolved	Trizek-WMF	T158332 Announce and follow up with communities group 2 about the New Filters for Recent changes Beta deployment
Resolved	Trizek-WMF	T158333 Announce and follow up with communities group 3 about the New Filters for Recent changes Beta deployment
Resolved	Trizek-WMF	T158335 Announce and follow up with communities group 4 about the New Filters for Recent changes Beta deployment
Resolved	Trizek-WMF	T158336 Announce and follow up with community group 1 about the New Filters for Recent changes Beta deployment
Resolved	Trizek-WMF	T156157 Contact Portuguese Wikipedia about testing ERI Recent Changes Beta project
Resolved	Trizek-WMF	T158042 Followup with Polish Wikipedia about testing ERI filters for Recent Changes
Resolved	• jmatazzoni	T161655 Damaging levels on Polish Wikipedia overlap too much
Resolved	• Catrope	T161767 Add more values to test_stats
Resolved	• Catrope	T161706 Review ORES prediction visibility on wikis where they are enabled by default
Resolved	SBisson	T161888 Make ORES prediction disappear when the edit is reviewed by someone else with Flagged Revisions
Resolved	Halfak	T163153 Communicate new beta prefs and changes to ORES users specifically
Resolved	SBisson	T159763 Enable parts of ORES extension by default and manage impacts on the RC Page and the RC page Preferences tab
Resolved	SBisson	T160475 Manage ORES preferences on Watchlist (and Contributions)
Resolved	SBisson	T160575 Conform ORES sensitivity levels to the new ERI standards
Resolved	• Catrope	T162831 Tweak ORES-Related Preferences for Watchlist and RC Page ahead of next release
Resolved	None	T159300 Turn off 'classic' ORES highlighting on the RC page

Event Timeline

• jmatazzoni created this task.Feb 13 2017, 9:20 PM

• jmatazzoni updated the task description. (Show Details)

• jmatazzoni updated the task description. (Show Details)Feb 13 2017, 9:27 PM

This seems good to me.

Aklapper mentioned this in T158001: Discussion: release RC Page filtering to non-ORES filters AND make ORES default.Feb 14 2017, 12:25 PM

Aklapper merged a task: T158001: Discussion: release RC Page filtering to non-ORES filters AND make ORES default.

The order of release is as follows, as per T150715:

First wiki

pt.wp

Group #2: wikis with ORES enabled, excluding en.wp

Persian Wikipedia
Dutch Wikipedia
Polish Wikipedia
Russian Wikipedia
Turkish Wikipedia
Wikidata
Czech Wikipedia (added recently--ck with @Halfak)

Group #3

en.wp

Group #4—non ORES

Everything else

@Catrope, does that look good to you? How do we know when it's time to move to the next group?

In T158004#3025694, @jmatazzoni wrote:

@Catrope, does that look good to you?

Looks good, thanks for putting this together.

How do we know when it's time to move to the next group?

After deploying to a group we'll wait at least a week for feedback and bug reports to come in. When we're satisfied that we have addressed all of (or enough of) the bugs and feedback, we'll set a date for moving to the next group. I feel like group1->group2 will probably take several weeks, and the later transitions will likely take less time.

• jmatazzoni updated the task description. (Show Details)Feb 14 2017, 6:13 PM

Just to clarify: Will users on ORES-enabled wikis be able to opt-out of the new filters?

• jmatazzoni moved this task from Untriaged to Product/Design Work on the Collaboration-Team-Triage (Collab-Team-Q3-Jan-Mar-2017) board.Feb 14 2017, 7:11 PM

In T158004#3026292, @Halfak wrote:

Just to clarify: Will users on ORES-enabled wikis be able to opt-out of the new filters?

Yes, this proposal does not merge or marry the RCFilters beta feature to ORES at all. Instead, it proposes that 1) the ORES beta feature preference be eliminated, with the non-intrusive parts (r markings and [Hide] probably good edits) made undisableable and the highlighting feature made an opt-in preference; and 2) an entirely separate, new beta feature preference be created for the new RCFilters UI.

Following up on what Roan said: If a user opts out of "New filters for edit review," they will still have ORES (in the form of the "r"s). Whether ORES highlighting is displayed depends on whether they are opted in to via the new "AI highlighting," or whatever we call it, preference.

Now, there is a question that I hadn't thought of. We said the new preference would be on the Watchlist Preferences page, and would control ORES shading for Watchlist and Contributions. We could

Make it so that, if the user is not opted in to "New filters for edit review", then the Watchlist pref also gives them RC page ORES shading (even though it's not on the (Recent Changes Prefs page)
Or we could just not provide "Classic" ORES shading on RC page at all—just make people take the new interface or don't do ORES on RC page.
Or, I suppose we could have an RC page preference that, what, would get grayed out/disabled when you select "New filters for edit review"? (Can we do that? Because there's another prefernce that should work this way, but selecting one does not gray out he other -- it just informs you in the description that if you pick one the other one won't work.)

Note that the only people for whom this would be an issue are 1) people who had opted in to ORES and then, after being migrated to the new features, turned OFF "New filters" (because these folks would have ORES shading pref turned on by default in the migration) and 2) people who just decided they want to turn on AI shading, but either don't want the "New filters" or just don't know about them.

@Pginer-WMF, what do you think is the way to go here?

• Quiddity unsubscribed.Feb 14 2017, 8:43 PM

Currently, ORES setting are in the RecentChanges preferences. Highlighting prefs should probably be here and should be enabled by default for users who currently have the ORES beta feature enabled.

I'm not sure what would make the most sense from a branding point of view, but I think that adding a "new filters" RecentChanges preference on top of the ORES beta feature would probably make more sense to current ORES users.

If I understand correctly, users who have ORES on their wiki will have the filters under the "ORES" label on Beta features, and those who don't have ORES on their wiki will have "Recent Changes Filters" (or something similar) on Beta features. What if a wiki gets ORES in the meantime?

I think all of this will be confusing, especially when I see the options to opt-out a part of a Beta feature.

Trizek-WMF updated the task description. (Show Details)Feb 15 2017, 6:43 PM

I've edited the description according to my meeting with @jmatazzoni. Polish Wikipedia (which has applied for the test) and Portuguese Wikipedia (I'm still contacting that wiki) will have the first release.

I've created a task concerning turning ORES by default: T158225: Enable the ORES good faith and damaging UI by default, on wikis that have these ORES models available (instead of behind a Beta Feature)

Trizek-WMF added a subtask: T158225: Enable the ORES good faith and damaging UI by default, on wikis that have these ORES models available (instead of behind a Beta Feature).Feb 15 2017, 7:15 PM

Stalled until T158225: Enable the ORES good faith and damaging UI by default, on wikis that have these ORES models available (instead of behind a Beta Feature) is done.

Trizek-WMF mentioned this in T158225: Enable the ORES good faith and damaging UI by default, on wikis that have these ORES models available (instead of behind a Beta Feature).Feb 16 2017, 5:29 PM

Trizek-WMF updated the task description. (Show Details)Feb 16 2017, 5:37 PM

• jmatazzoni renamed this task from Discussion: release RC Page filtering to non-ORES wikis to Release RC Page filtering to non-ORES wikis.Feb 22 2017, 9:56 PM

• jmatazzoni mentioned this in T159007: Implement the beta preference option for RC Filters project.Feb 24 2017, 10:40 PM

• jmatazzoni removed a parent task: T144457: Invite users to opt in to the RC Filters beta from the RC page, and educate them about its features.Feb 24 2017, 11:16 PM

• jmatazzoni edited projects, added Collaboration-Team-Triage, Tracking-Neverending; removed Collaboration-Team-Triage (Collab-Team-Q3-Jan-Mar-2017).Feb 27 2017, 7:50 PM

• jmatazzoni moved this task from Untriaged to Tracking tickets on the Collaboration-Team-Triage board.

• jmatazzoni closed subtask T158225: Enable the ORES good faith and damaging UI by default, on wikis that have these ORES models available (instead of behind a Beta Feature) as Resolved.Mar 14 2017, 9:15 PM

Jdforrester-WMF changed the task status from Stalled to Open.Mar 18 2017, 2:54 AM

Trizek-WMF added a subtask: T158335: Announce and follow up with communities group 4 about the New Filters for Recent changes Beta deployment .Mar 20 2017, 8:59 AM

Trizek-WMF updated the task description. (Show Details)

Trizek-WMF reopened subtask T158225: Enable the ORES good faith and damaging UI by default, on wikis that have these ORES models available (instead of behind a Beta Feature) as Open.Mar 20 2017, 9:04 AM

Shizhao added a project: User-notice.Mar 21 2017, 3:50 AM

Trizek-WMF closed subtask T158225: Enable the ORES good faith and damaging UI by default, on wikis that have these ORES models available (instead of behind a Beta Feature) as Resolved.Mar 21 2017, 12:37 PM

Drafted on the next Tech News (week 13).

Trizek-WMF moved this task from To Triage to In current Tech/News draft on the User-notice board.Mar 23 2017, 5:22 PM

Johan moved this task from In current Tech/News draft to Already announced/Archive on the User-notice board.Mar 29 2017, 11:31 AM

Trizek-WMF changed the status of subtask T158335: Announce and follow up with communities group 4 about the New Filters for Recent changes Beta deployment from Stalled to Open.Apr 10 2017, 2:38 PM

• Whatamidoing-WMF mentioned this in T163337: Job queue corruption after codfw switch over (Queue growth, duplicate runs).Apr 21 2017, 5:16 PM

Change 343439 had a related patch set uploaded (by Catrope):
[operations/mediawiki-config@master] Enable RCFilters beta feature on all wikis except wikidatawiki, nlwiki, cswiki, etwiki and hewiki

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

gerritbot added a project: Patch-For-Review.Apr 21 2017, 6:37 PM

Trizek-WMF updated the task description. (Show Details)Apr 24 2017, 8:56 AM

Change 343439 merged by jenkins-bot:
[operations/mediawiki-config@master] Enable RCFilters beta feature on all wikis except wikidatawiki, nlwiki, cswiki, etwiki and hewiki

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

https://cs.wikipedia.org/wiki/Speciální:Poslední_změny (cswiki RC) down for me with beta ORES enabled. Otherwise works. Not sure but may be related to the config change.

https://www.wikidata.org/w/index.php?title=Special:RecentChanges (wikidatawiki) as well.

matej_suchanek mentioned this in T163696: Special:RecentChanges in wikidata/cs/etwiki displays error due to config screwup.Apr 24 2017, 3:21 PM

@matej_suchanek, it works for me. Maybe a gadget or script conflict: what about the two following links with ORES enabled: