Coordinate with Tech Ambassadors for graduating New Filters on Watchlist out of beta
Open, HighPublic

Description

New Filters on Watchlist are graduating out of beta. This is a great opportunity to work with Tech ambassadors. :)

[Announcement to share to the communities]

Plans to graduate the New Filters on Watchlist out of beta

Collaboration team is announcing plans to graduate the New Filters for Edit Review out of beta on Watchlist by late June or early July. After launch, this suite of improved edit-search tools will be standard on all wikis. Individuals who prefer the existing Watchlist interface will be able to opt out by means of a new preference.

The New Filters introduce an easier yet more powerful user interface to Watchlist as well as a whole list of filters and other tools that make reviewing edits more efficient, including live page updating, user-defined highlighting,the ability to create special-purpose filter sets and save them for re-use and (on wikis with ORES enabled) predictive filters powered by machine learning. If you’re not familiar with the New Filters, please give them a try on Watchlist by activating the New Filters beta feature. In particular, it would be very helpful if you can test the new functionality with your local gadgets and configurations. The documentation pages provide guidance on how to use the many new tools you’ll discover.

Over 70,000 people have activated the New Filters beta, which has been in testing on Watchlist for more than eight months. We feel confident that the features are stable and effective, but if you have thoughts about these tools or the beta graduation, please let us know on the project talk page. In particular, tell us if you know of a special incompatibility or other issue that makes the New Filters problematic on your wiki. We’ll examine the blocker and may delay release on your wiki until the issue can be addressed.

What people will see

When the deployment will be done, people accessing their watchlist will get a pop-up explaining what's going on (T195427) and will have an option to opt-out (T195431).

Schedule

  • First batch of wikis: all wikis except the ones listed on T171030#3549355 - week of the 18th of June.
  • Second batch: al remaining wikis (aka the ones listed on T171030#3549355) - week of the 25th of June if things go well, later if not.
  • Third batch, for wikis with concerns and actionable blockers, identified as such by the development team (whether they are sensible, consistent with the project, actionable, realistic, measurable…): not later that the end of July.

How to coordinate?

If you want to assist the deployment, please share that announcement to your community and copy the link here. Please also share your ideas about how to announce that:

  • on village pump
  • on a local newsletter
  • on the watchlist notice (suggested by @Kaartic)
  • on any language group regarding to your wiki or group of wikis
  • ...

Wikis that would not be listed here will be supported by @Trizek-WMF in T195519.

Questions?

If you have questions or feedback about that process or the deployment in itself, please share them below.
If you have questions or feedback about the filters, please post them on on the project talk page.

Trizek-WMF triaged this task as High priority.
Restricted Application added a project: Collaboration-Team-Triage. · View Herald TranscriptWed, May 30, 6:01 PM
Trizek-WMF moved this task from Backlog to On-wiki sharing needed ASAP on the Tech-Ambassadors board.
Trizek-WMF moved this task from Untriaged to Hot on the Collaboration-Team-Triage board.
Trizek-WMF moved this task from Backlog to June on the Community-Liaisons (Apr-Jun-2018) board.
Trizek-WMF renamed this task from Coordinate with Tech Ambassadors for graduating New Filters on Watchlist out of beta (this June!) to Coordinate with Tech Ambassadors for graduating New Filters on Watchlist out of beta .
Trizek-WMF updated the task description. (Show Details)Wed, May 30, 6:22 PM
Trizek-WMF updated the task description. (Show Details)
jmatazzoni updated the task description. (Show Details)Thu, May 31, 1:05 AM
jmatazzoni updated the task description. (Show Details)

Since I haven't received any information about Tech Ambassadors warning their communities, I'll post messages on all wiki soon.

Hi @Trizek-WMF, as I see in the description, there is a way to to opt-out the new filters. Is this option available in User Preferences and it will available "forever" (like as the old-plain wikieditor)?. My community is very special :)

Hi, after contact Trizek on IRC, I've sent a Spanish message in the Village Pump on all Wikimedia projects.

Anooprao added a subscriber: Anooprao.EditedTue, Jun 5, 4:38 PM

I have added one line introduction on Kannada wikipedia https://kn.wikipedia.org/wiki/ವಿಕಿಪೀಡಿಯ:ಅರಳಿ_ಕಟ್ಟೆ#ಪ್ರಾಯೋಗಿಕ_ವೀಕ್ಷಣಾ_ಪಟ್ಟಿ

You can still send them formal message.
Thanks

Thank you @Anooprao, @Kaartic, @Stryn, and @Superzerocool! That's great!

I plan to post an untranslated, more formal message tomorrow morning UTC on wikis what haven't been covered by Tech Ambassadors.

Is this option available in User Preferences and it will available "forever" (like as the old-plain wikieditor)?.

The opt-out option will be:

  • on the Watchlist when the user will access the new watchlist system for the first time
  • on Preferences

It is possible to opt-out anytime, and there is no plan to remove the "old" watchlist.

Kaartic added a comment.EditedWed, Jun 6, 1:27 PM

A general suggestion about announcing the graduation of any beta feature. It would be nice if there is a notice about this below the corresponding beta feature in Special:Preferences#mw-prefsection-betafeatures. Though the audience might not be so high, it would still gains some attention (if designed properly) and would possibly kindle someone to provide suggestion when it's most needed. When it comes to propagating news we should do it in as much places as we cane and I find Special:Preferences to be yet another possibility.

That's a good idea, @Kaartic.

Trizek-WMF added a comment.EditedWed, Jun 6, 4:45 PM

I confirm that the deployment will happen in two phases on the wikis:

  • June 18, all wikis except the ones below
  • June 25 for the following wikis:
    • Commons
    • Meta
    • Wikispecies
    • Wikidata
    • MediaWikiwiki
    • Wiktionary user group
    • Wikisource user group
    • The following Wikipedias
      • English
      • German
      • Dutch
      • Spanish
      • Catalan
      • Portuguese
      • Italian
      • Polish
      • Czech
      • Hungarian
      • Russian
      • Arabic
      • Farsi
      • Korean
      • Chinese
      • Chinese-yue
      • Japanese
      • Indonesian
      • Swedish
      • Norwegian
      • Finnish
      • Danish
      • French
      • Hebrew

Thank you @Kaartic and @Oriciu!

I'll post on all wikis on the list above tomorrow if not done. The message is drafted here.

@Trizek-WMF Someone seems to be detailing about issues he finds with the new edit filters update in enwikinews. The discussion could be found at https://en.wikinews.org/wiki/Wikinews:Water_cooler/technical#RfC:_Plans_to_graduate_the_New_Filters_on_Watchlist_out_of_beta.

I'm not pretty sure, how to handle this. Could you please help with this?

If possible, can that user share those issues on the feedback page? That page is monitored by the product manager and some developers. They will be able to reply faster than me (timezones). In any case, I'll reply tomorrow. Thank you, and sorry you have to face that.

Thank you, and sorry you have to face that.

Just for the sake of clarification, are feeling sorry that I had to face that situation OR are you mentioning that it's something I would have to face ?

In the former case, I'm not feeling bad about it and am aware that it happens in these situations. I just thought I wasn't mature enough to handle this one myself and didn't want to screw by trying to handle it myself ;-) So, I asked your help. Thanks!

Thank you, and sorry you have to face that.

Just for the sake of clarification, are feeling sorry that I had to face that situation OR are you mentioning that it's something I would have to face ?

I mean you have to face that situation.

In the former case, I'm not feeling bad about it and am aware that it happens in these situations. I just thought I wasn't mature enough to handle this one myself and didn't want to screw by trying to handle it myself ;-) So, I asked your help. Thanks!

@jmatazzoni has step in and is handling the case. :)

Message sent to the list.

I have tried to double check my distribution list but I have a duplicate. Anyway, it is better to announce it twice than not announcing it at all. :)

We didn't get any message on hewiki Village Pump

The message is drafted here you can post it yourself. @IKhitron

Of course, and I know where is the draft. But maybe Trizek did not do this in purpose. And maybe, it's a bug, on more wikis.

Stryn added a comment.Thu, Jun 7, 3:02 PM

Finnish Wikipedia also twice (1 on two different village pumps), but well let it be then.

Got it now on wrong page, I'm moving it.

Finnish Wikipedia also twice (1 on two different village pumps), but well let it be then.

Oops, sorry. :/

Got it now on wrong page, I'm moving it.

Can you tell me what is the right place, so that I can change my targets?

Got it now on wrong page, I'm moving it.

Can you tell me what is the right place, so that I can change my targets?

On [[w:he:WP:מזנון]] - Village Pump. Sometimes, depends on the content, we move it to the News page. I believe you saw it moved once, and thought it's always should be the target, so you fixed it.

Can you tell me what is the right place, so that I can change my targets?

You can use the list on https://meta.wikimedia.org/wiki/Distribution_list/Global_message_delivery, or the technical one. Please, update these pages if necessary.

The page you mentioned has the right address, and it haven't been updated today. What is the technical one?

Thank you, but it isn't the right list eithet.

I've posted a request to have a message on MediaWiki_talk:Watchlist-messages for English Wikipedia.

If your wiki has that messaging system, you should use it to warn users about that change.

You can use the list on https://meta.wikimedia.org/wiki/Distribution_list/Global_message_delivery, or the technical one. Please, update these pages if necessary.

I've used https://meta.wikimedia.org/wiki/Distribution_list/Technical_Village_Pumps_distribution_list
If the list is not up to date, please edit it.

Done. Actially, hewiki wasn't there at all

Kaartic added a comment.EditedFri, Jun 8, 12:56 PM

There seems to be a strong opposition to deploy the new Special:Watchlist in wikinews. See linked discussion.

There seems to be a strong opposition to deploy the new Special:Watchlist in wikinews. See linked discussion.

I don't perceive it as an opposition. People give opinions but don't provide anything reasonable to justify that block. As they say, they give opinion "if consensus is considered here", which is not really the case.

It is possible to stop the deployment process, by giving specific feedback. The community has been asked to elaborate on special incompatibilities or other issues that makes the New Filters problematic on their wiki from a technical perspective, preferably as bug reports. There are no update since June 8th about that.

There are no update since June 8th about that.

I suspect there is an update.

Someone out there[1] seems to be stating the inability for IPs to opt-out of the new RC UI as an issue. They find this to be an issue because of the possibility that the new UI might require more processing power than the old one (which I suspect to be true). and so IPs who contribute with a low-end device might find it difficult to use the new UI. They hope this should get solved failing which they expect to lose a valuable IP contributor from their community. See referred comment for clear details.

I guess we should consider providing a way for IPs of the new RC UI similar to how Page previews were allowed to be enable or disabled for IPs.

[1]: If it's not clear which comment I'm referring to, see Gryllida's comment timestamped 21:09, 12 June 2018

I've asked for clarifications, because all that feedback is unclear to me. I looking for actionable blockers.

Concerning the IPs opting out features in general, well, that's a discussion happening since a while. Why don't people use accounts instead of identifiable IPs? Have a way to opt-out would mean a cookie, cookie that would expire at some point. That's a limited option. Also, I've heard that page previews' disabling feature is not that used. Does it worth it?

Other than that, I'm a bit sad to see those blockers on RCs raised up almost 6 months after the release by default, by people who know where to report those issues. But that's better to hear that now than never, hoping that we can fix the issue (if there is one actionable one).

Kaartic added a comment.EditedWed, Jun 13, 1:27 PM

Concerning the IPs opting out features in general, well, that's a discussion happening since a while. Why don't people use accounts instead of identifiable IPs?

I'm curious about that too particularly because that feedback states "Internet and privacy issues" for contributing as IPs. I've asked the user about that in their talk page.

Does it worth it?

Maybe ;-) If it's not technically difficult to allow IP contributors to disable the new feature, it might worth the try as we could be making more users happy and be a little more unbiased to IP contributors :-)

But that's better to hear that now than never,

Yeah, that's what I thought too.

hoping that we can fix the issue (if there is one actionable one).

Let's hope for an actionable one to come up.

hoping that we can fix the issue (if there is one actionable one).

Let's hope for an actionable one to come up.

Yeah, I don't want people to be frustrated because of a real blocker.

News: next week is a no-deploys week. The deployment is delayed to June 25 for the first group and early July for the second one.

We also have received several feedback from people about loading speed and we are investigating it: T197168: Investigate report of slow Watchlist load times