Page MenuHomePhabricator
Create Task
Maniphest 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)
Closed, ResolvedPublic
Actions

Description

The ORES good faith and damaging tests are available for use on the wikis below, most of which offer ORES as a beta feature. Enabling ORES by default on these wikis will simplify users' interaction with ORES and the new filtering interface (e.g., users won't have to select both beta options to get all the benefits of the new tools).

  • Portuguese Wikipedia
  • Polish Wikipedia
  • Persian Wikipedia
  • Dutch Wikipedia
  • Polish Wikipedia
  • Russian Wikipedia
  • Turkish Wikipedia
  • Wikidata
  • Czech Wikipedia
  • English Wikipedia

What this means

  • On ORES wikis, ORES for edit review (specifically, the good faith, damaging and revert tests) will be enabled by default. I.e., there will be no ORES beta option.
  • In the future, at such time as new ORES betas are created (for Discover, anti-harrassment, or whatever), those will be new betas. I.e., we are making default ONLY the ORES functions that are currently available and displayed to the public through the existing beta.
  • All users will get the red "R" on review pages that means "may be damaging and should be reviewed." This feature is not intrusive.
  • Existing ORES users will also be migrated automatically to the new beta option, "New Filters for Edit Review."
  • Existing ORES beta users will continue to get the "classic" ORES display, with colored shading, on Watchlist and Contributions.

Stuff that needs to be handled


==Preferences !![all functionality below moved to T159763]!!

~~**Hide probably good edits from recent changes** This Recent Changes option currently appears only after users have selected the ORES beta, and is unselected by default. ~~
- ~~It will now become standard for everyone (still unselected by default)~~
- ~~If it was selected by existing ORES users or is selected by new users, then on the RC page, activate the following filter and display it as a default in the Active Filter Display Area: May have problems.~~
-~~Meanwhile, re-word the preference to align it with the new functionality, like so: "Show only edits that may have problems (and hide probably good edits)."~~

- ~~**Highlight probably damaging edits on Watchlist and Contributions (using ORES)** Add this __new Preference__ to the Watchlist prefs in the "Revision Scoring" section. It turns on classic ORES shading on Watchlist and Contributions. ~~
- ~~For existing ORES users, this will be turned on by default when they are migrated. ~~
- ~~For everyone else, this preference will be off by default. ~~
- ~~It's expected that as we move more pages to the new interface, this preference will control fewer and fewer pages. One day, we'd like to replace "classic" ORES entirely.This preference in no way should be read as committing to supporting this. ~~

- ~~**Ores Sensitivity** The existing subsidiary preference for ORES Sensitivity will be grouped with the new "Highlight probably damaging edits" preference, because it depends on it. It is subsidiary.~~
- ~~It will continue doing whatever it does now, but not for Recent Changes. ~~

Related Objects
Search...

StatusSubtypeAssignedTask
 DuplicateQgilT125545 Phabricator Q&A session for Community Liaisons
 ResolvedQgilT116025 Goal: Align Community Liaison and Developer Relations project management practices
 ResolvedQgilT119387 Community Liaison and Developer Relation quarterly goals for January - March 2016
 DeclinedNoneT121500 Unify product documentation for users to make it easier to share, translate and edit
 ResolvedJohanT128790 Translation strategy – act and refine
 ResolvedTrizek-WMFT129088 Create an easy to maintain glossary to facilitate documentation translation (help pages and technical documentation)
 Resolved• jmatazzoniT145875 Create and maintain Edit Review Improvements documentation
 Resolved• DannyHT171977 Annual Plan 2017-2018, Audiences 5: Increase current editor retention and engagement
 Resolved• DannyHT171981 Annual Plan 2017-2018, Audiences 5, Goal 2: Give better ways to monitor contributions
 Resolved• jmatazzoniT157642 Graduate New Filters UX out of beta on Recent Changes on ALL wikis
 Resolved• jmatazzoniT144458 Launch ERI RC page features as a Beta Feature to all wikis
 Resolved• jmatazzoniT150715 Release strategy for RC page improvements: what wikis get the new features when?
 ResolvedTrizek-WMFT146669 Create dedicated pages for ERI Recent Changes Beta project
 Resolved• jmatazzoniT141449 Define Edit Review Improvements glossary
 Resolved• jmatazzoniT145157 Research current "new user" definitions and consider whether we need a different name for the ReviewStream and RC page “new user” flag / filter
 Resolved• jmatazzoniT151477 Improve Filters for Special:Recent Changes documentation page on mediawiki.org
 ResolvedTrizek-WMFT154889 Mark Edit Review Improvements glossary for translation
 ResolvedPginer-WMFT147632 Prototype an improved version of Recent Change designs
 Resolved• jmatazzoniT146333 Research how to present ORES scores to users in a way that is understandable and meets their reviewing goals
 Resolved• CatropeT150959 Integrate a feedback page link in Recent Changes Beta filters
 ResolvedPginer-WMFT160063 Explore ways to represent visually the ORES-related filters and associated tradeoffs
 Resolved• jmatazzoniT161015 Add screenshots to the help pages for Recent Changes Filters Beta project
 OpenNoneT142782 Explore process for turning on RCPatrol for English and other relevant wikis
 ResolvedTrizek-WMFT158004 Release RC Page filtering to non-ORES wikis
 ResolvedTrizek-WMFT158225 Enable the ORES good faith and damaging UI by default, on wikis that have these ORES models available (instead of behind a Beta Feature)
 ResolvedTrizek-WMFT159223 Inform communities about the release of the ORES good faith and damaging UI by default
 ResolvedTrizek-WMFT146972 Announce and follow up with communities about the New Filters for Recent changes Beta deployment
 ResolvedTrizek-WMFT158332 Announce and follow up with communities group 2 about the New Filters for Recent changes Beta deployment
 ResolvedTrizek-WMFT158333 Announce and follow up with communities group 3 about the New Filters for Recent changes Beta deployment
 ResolvedTrizek-WMFT158335 Announce and follow up with communities group 4 about the New Filters for Recent changes Beta deployment
ResolvedTrizek-WMFT158336 Announce and follow up with community group 1 about the New Filters for Recent changes Beta deployment
 ResolvedTrizek-WMFT156157 Contact Portuguese Wikipedia about testing ERI Recent Changes Beta project
 ResolvedTrizek-WMFT158042 Followup with Polish Wikipedia about testing ERI filters for Recent Changes
 Resolved• jmatazzoniT161655 Damaging levels on Polish Wikipedia overlap too much
 Resolved• CatropeT161767 Add more values to test_stats
 Resolved• CatropeT161706 Review ORES prediction visibility on wikis where they are enabled by default
 ResolvedSBissonT161888 Make ORES prediction disappear when the edit is reviewed by someone else with Flagged Revisions
 ResolvedHalfakT163153 Communicate new beta prefs and changes to ORES users specifically
 ResolvedSBissonT159763 Enable parts of ORES extension by default and manage impacts on the RC Page and the RC page Preferences tab
 ResolvedSBissonT160475 Manage ORES preferences on Watchlist (and Contributions)
 ResolvedSBissonT160575 Conform ORES sensitivity levels to the new ERI standards
 Resolved• CatropeT162831 Tweak ORES-Related Preferences for Watchlist and RC Page ahead of next release
ResolvedNoneT159300 Turn off 'classic' ORES highlighting on the RC page

Event Timeline

Trizek-WMF created this task.Feb 15 2017, 7:04 PM
Restricted Application added a project: Machine-Learning-Team. · View Herald TranscriptFeb 15 2017, 7:04 PM
Trizek-WMF added a comment.EditedFeb 15 2017, 7:05 PM

I've cc-ed some people who can help outreaching that change.

Questions to solve before we send the message:

  • is it possible to totally opt-out that ORES feature?
  • When is the release?

Assigned to @jmatazzoni to draft the message.

Trizek-WMF moved this task from Backlog to February on the Community-Relations-Support (Jan-Mar 2017) board.Feb 15 2017, 7:06 PM
Trizek-WMF updated the task description. (Show Details)Feb 15 2017, 7:13 PM
Trizek-WMF mentioned this in T158004: Release RC Page filtering to non-ORES wikis.Feb 15 2017, 7:15 PM
Trizek-WMF added a parent task: T158004: Release RC Page filtering to non-ORES wikis.
Ladsgroup added a comment.Feb 15 2017, 8:43 PM

One quick note, ORES review tool is not enabled in cswiki but it will be done this week (if I have some time to make it happen in SWAT).
Practically there is no way to disable ORES in the extension. The extension can be modified in a way to add that very easily. If this is needed, please make a subtask and assign it to me. I get it done.

Halfak edited projects, added Machine-Learning-Team (Active Tasks); removed Machine-Learning-Team.Feb 16 2017, 3:41 PM
Halfak moved this task from Parked to Monitor (long term) on the Machine-Learning-Team (Active Tasks) board.Feb 16 2017, 3:48 PM
Trizek-WMF renamed this task from Tell wikis that use ORES being turned as a by-default feature on wikis that have it as a Beta feature to Turn ORES for edit review as a by-default feature on wikis that have it as a Beta feature.Feb 16 2017, 5:29 PM
Trizek-WMF updated the task description. (Show Details)
Trizek-WMF added a subtask: T146972: Announce and follow up with communities about the New Filters for Recent changes Beta deployment.
Trizek-WMF mentioned this in T146972: Announce and follow up with communities about the New Filters for Recent changes Beta deployment.
Trizek-WMF changed the status of subtask T146972: Announce and follow up with communities about the New Filters for Recent changes Beta deployment from Open to Stalled.
Trizek-WMF triaged this task as High priority.Feb 16 2017, 5:31 PM
Trizek-WMF added a subtask: T158332: Announce and follow up with communities group 2 about the New Filters for Recent changes Beta deployment.Feb 16 2017, 5:39 PM
Trizek-WMF added a subtask: T158336: Announce and follow up with community group 1 about the New Filters for Recent changes Beta deployment.Feb 16 2017, 5:44 PM
Trizek-WMF added a comment.Feb 16 2017, 5:52 PM
In T158225#3030821, @Ladsgroup wrote:

One quick note, ORES review tool is not enabled in cswiki but it will be done this week (if I have some time to make it happen in SWAT).

Thank you for that information. By the time we will follow up with that wiki, they will have it.

Then the question is to know if they need time to have it tested, or if a deployment by default is possible with a few disagreements. @jmatazzoni, @Halfak, thoughts?

Halfak renamed this task from Turn ORES for edit review as a by-default feature on wikis that have it as a Beta feature to Enable the ORES review tool by-default feature on wikis that have it as a Beta feature.Feb 16 2017, 6:11 PM
Halfak renamed this task from Enable the ORES review tool by-default feature on wikis that have it as a Beta feature to Enable the ORES review tool by-default on wikis that have it as a Beta feature.
Trizek-WMF mentioned this in T158042: Followup with Polish Wikipedia about testing ERI filters for Recent Changes.Feb 17 2017, 2:54 PM
Trizek-WMF mentioned this in T156157: Contact Portuguese Wikipedia about testing ERI Recent Changes Beta project.
matej_suchanek mentioned this in T151611: Enable ORES Review Tool on Czech Wikipedia.Feb 19 2017, 5:08 PM
Trizek-WMF mentioned this in T158441: Turn on ORES good faith test model in production for all supported wikis targeted for RC Page release.Feb 20 2017, 2:50 PM
• jmatazzoni removed • jmatazzoni as the assignee of this task.Feb 21 2017, 5:58 PM
• jmatazzoni added projects: Collaboration-Team-Triage (Collab-Team-Q3-Jan-Mar-2017), Edit-Review-Improvements-RC-Page.
• jmatazzoni merged a task: T158441: Turn on ORES good faith test model in production for all supported wikis targeted for RC Page release.
• jmatazzoni added subscribers: • jmatazzoni, Mooeypoo, Pginer-WMF and 3 others.
• jmatazzoni added a subscriber: • Mattflaschen-WMF.
Trizek-WMF added a comment.Feb 22 2017, 4:13 PM

Four groups have been defined for the rollout of Filters for Recent changes. We should do the change at the same time:

• jmatazzoni moved this task from Untriaged to Blocked on the Collaboration-Team-Triage (Collab-Team-Q3-Jan-Mar-2017) board.Feb 22 2017, 10:09 PM
• jmatazzoni renamed this task from Enable the ORES review tool by-default on wikis that have it as a Beta feature to Enable the ORES good faith and damaging models by default on wikis that have ORES as a Beta, and communicate this to the communities.Feb 22 2017, 11:02 PM
Qgil subscribed.Feb 23 2017, 12:21 PM

This task scheduled for Community-Relations-Support (Jan-Mar 2017) needs an owner. Is that you, @Trizek-WMF?

Trizek-WMF removed a project: Community-Relations-Support (Jan-Mar 2017).Feb 23 2017, 2:49 PM
In T158225#3049301, @Qgil wrote:

This task scheduled for Community-Relations-Support (Jan-Mar 2017) needs an owner. Is that you, @Trizek-WMF?

No. That task is covering multiple points. The ongoing discussion is about turning the relevant ORES models by default at the same time as the release of the new RC Filters. That would be covered by T146972: Announce and follow up with communities about the New Filters for Recent changes Beta deployment and sub-tasks. I'm still waiting for a confirmation from @jmatazzoni.

• jmatazzoni updated the task description. (Show Details)Feb 25 2017, 12:14 AM

@Trizek-WMF, I'm reworking this task strictly for implementation, and taking out the part about "informing the communities." You should make a separate task for communication. I took out the verbiage that was in the task description relating to "informing." Here it is, below, for your convenience:

  • It won’t effect people that much, except for the red “r”, which can make it black locally if they want to
  • There will be a new preference to turn on highlighting on the non-RC pages that have ORES (Watchlist and Contributions).
  • If you had the highlighting before, you will have it, if you haven’t enabled the Beta feature, you don’t have the highlighting.
  • ...

Steps:

  • Draft a message to be posted on these wikis
  • Decide of a schedule to send a message one week before the release and the day before that change
  • Identify places where to post that message (village pumps - technical ones, patrollers boards...)
• jmatazzoni renamed this task from Enable the ORES good faith and damaging models by default on wikis that have ORES as a Beta, and communicate this to the communities to Enable the ORES good faith and damaging models by default on wikis that have these ORES models available. .Feb 25 2017, 1:09 AM
• jmatazzoni updated the task description. (Show Details)
• jmatazzoni mentioned this in T150059: Make sure all Preferences for Recent Changes are compatible with new filtering system/page tools (and that users' preferences carry over).Feb 25 2017, 1:12 AM
• jmatazzoni moved this task from Blocked to Ready for Pickup on the Collaboration-Team-Triage (Collab-Team-Q3-Jan-Mar-2017) board.

I don't think this is blocked anymore. Is it? Moving to RFP.

• Mattflaschen-WMF renamed this task from Enable the ORES good faith and damaging models by default on wikis that have these ORES models available. to 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 25 2017, 1:25 AM
Trizek-WMF created subtask T159223: Inform communities about the release of the ORES good faith and damaging UI by default.Feb 28 2017, 1:51 PM
In T158225#3054465, @jmatazzoni wrote:

@Trizek-WMF, I'm reworking this task strictly for implementation, and taking out the part about "informing the communities." You should make a separate task for communication. I took out the verbiage that was in the task description relating to "informing." Here it is, below, for your convenience:

  • It won’t effect people that much, except for the red “r”, which can make it black locally if they want to
  • There will be a new preference to turn on highlighting on the non-RC pages that have ORES (Watchlist and Contributions).
  • If you had the highlighting before, you will have it, if you haven’t enabled the Beta feature, you don’t have the highlighting.
  • ...

Steps:

  • Draft a message to be posted on these wikis
  • Decide of a schedule to send a message one week before the release and the day before that change
  • Identify places where to post that message (village pumps - technical ones, patrollers boards...)

Sure, it will be more clear.

Trizek-WMF removed a subtask: T146972: Announce and follow up with communities about the New Filters for Recent changes Beta deployment.Feb 28 2017, 1:53 PM
Qgil unsubscribed.Mar 1 2017, 4:34 PM
• Mattflaschen-WMF mentioned this in T158459: Add ORES to RCFilters.Mar 3 2017, 12:55 AM
• Catrope mentioned this in T159763: Enable parts of ORES extension by default and manage impacts on the RC Page and the RC page Preferences tab.Mar 6 2017, 10:30 PM
• Catrope created subtask T159763: Enable parts of ORES extension by default and manage impacts on the RC Page and the RC page Preferences tab.
• jmatazzoni added a subtask: T159300: Turn off 'classic' ORES highlighting on the RC page.Mar 6 2017, 10:42 PM
• jmatazzoni closed this task as Resolved.Mar 14 2017, 9:14 PM
• jmatazzoni updated the task description. (Show Details)
SBisson closed subtask T159300: Turn off 'classic' ORES highlighting on the RC page as Invalid.Mar 16 2017, 5:36 PM
Jdforrester-WMF added a project: User-notice.Mar 18 2017, 2:55 AM
Jdforrester-WMF subscribed.

This will happen on w/c 26 March.

Trizek-WMF reopened this task as Open.Mar 20 2017, 9:04 AM
In T158225#3111761, @Jdforrester-WMF wrote:

This will happen on w/c 26 March.

Wait... It was supposed to be done by rollouts (T146972), to migrate automatically users to the New Filters for Edit Review. What did I missed?

• Catrope added a comment.Mar 20 2017, 5:07 PM
In T158225#3113719, @Trizek-WMF wrote:
In T158225#3111761, @Jdforrester-WMF wrote:

This will happen on w/c 26 March.

Wait... It was supposed to be done by rollouts (T146972), to migrate automatically users to the New Filters for Edit Review. What did I missed?

I think that's what he means.

Trizek-WMF closed this task as Resolved.Mar 21 2017, 12:37 PM
Trizek-WMF claimed this task.
In T158225#3115021, @Catrope wrote:
In T158225#3113719, @Trizek-WMF wrote:
In T158225#3111761, @Jdforrester-WMF wrote:

This will happen on w/c 26 March.

Wait... It was supposed to be done by rollouts (T146972), to migrate automatically users to the New Filters for Edit Review. What did I missed?

I think that's what he means.

That's how it has been clarified orally.

Trizek-WMF changed the status of subtask T158332: Announce and follow up with communities group 2 about the New Filters for Recent changes Beta deployment from Stalled to Open.Mar 21 2017, 3:59 PM
Trizek-WMF moved this task from To Triage to In current Tech/News draft on the User-notice board.Mar 23 2017, 5:17 PM
Trizek-WMF closed subtask T159223: Inform communities about the release of the ORES good faith and damaging UI by default as Resolved.Mar 24 2017, 3:57 PM
• jmatazzoni closed subtask T159763: Enable parts of ORES extension by default and manage impacts on the RC Page and the RC page Preferences tab as Resolved.Mar 29 2017, 12:14 AM
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
• jmatazzoni reopened subtask T159300: Turn off 'classic' ORES highlighting on the RC page as Open.Apr 3 2017, 8:50 PM
• jmatazzoni closed subtask T159300: Turn off 'classic' ORES highlighting on the RC page as Resolved.Apr 18 2017, 1:00 AM
Trizek-WMF closed subtask T158332: Announce and follow up with communities group 2 about the New Filters for Recent changes Beta deployment as Resolved.Apr 26 2017, 4:05 PM
Trizek-WMF closed subtask T158336: Announce and follow up with community group 1 about the New Filters for Recent changes Beta deployment as Resolved.May 9 2017, 10:12 AM
awight moved this task from Monitor (long term) to Completed on the Machine-Learning-Team (Active Tasks) board.Jul 3 2017, 5:50 PM
Qgil added a project: Community-Relations-Support (Jan-Mar 2017).Jul 12 2017, 3:44 PM
Qgil moved this task from February to March on the Community-Relations-Support (Jan-Mar 2017) board.
Ladsgroup edited projects, added User-notice-archive; removed User-notice.Aug 13 2022, 1:53 PM
Restricted Application added a subscriber: Huji. · View Herald TranscriptAug 13 2022, 1:53 PM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits