Change Details

It is time to test out topic matching in production. It is currently only available to users who run the code below to turn on the hidden preference. We want to have all test results by Monday, Jan 20 so we can plan to expose the feature to newcomers on Tuesday, Jan 21. Below are instructions for how to test. [X] Czech [] Korean [] Vietnamese [] Arabic 1. Go to the newcomer homepage in your wiki. 2. Reset the suggested edits workflow for your user. Do this by opening your browser tools (by right-clicking and choosing "Inspect") and running this in the console: `new mw.Api().saveOption('growthexperiments-homepage-suggestededits-activated', 0).done( function() { window.location.reload() });` 3. Enable topic matching by running this in the console: `new mw.Api().saveOption('growthexperiments-homepage-suggestededits-topics-enabled', 1).done( function() { window.location.reload() });` 4. Go through the workflow of initiating suggested edits, choosing topics, and changing topics. Try everything out! You can always re-run Step 2 to reset the whole workflow and see the initiation pieces again. 5. Note any issues relating to: ** Missing or incorrect translations ** Interface behaving strangely or looking weird ** When you select a topic, get results, then switch topics and switch back, you are supposed to get different results than you got the first time. We want to make sure that not all users who select "Music" get the same article suggestions. ** Poor topic results. This is important, especially because @Dyolf77_WMF noted in T242400 that results in the module looked different than the ones coming over the API. Please try out several different topics and think about whether the performance is better or worse than previous tests. 6. Try all of this on your mobile device. You can reset the workflow on desktop with Step 2 so that you can try it on mobile. Please post any issues or concerns as comments on this task. If you have to update translations, let us know when you've done that in Translatewiki so that @Catrope can update them manually before the next train runs.

It is time to test out topic matching in production. It is currently only available to users who run the code below to turn on the hidden preference. We want to have all test results by Monday, Jan 20 so we can plan to expose the feature to newcomers on Tuesday, Jan 21. Below are instructions for how to test. [X] Czech [x] Korean [] Vietnamese [x] Arabic 1. Go to the newcomer homepage in your wiki. 2. Reset the suggested edits workflow for your user. Do this by opening your browser tools (by right-clicking and choosing "Inspect") and running this in the console: `new mw.Api().saveOption('growthexperiments-homepage-suggestededits-activated', 0).done( function() { window.location.reload() });` 3. Enable topic matching by running this in the console: `new mw.Api().saveOption('growthexperiments-homepage-suggestededits-topics-enabled', 1).done( function() { window.location.reload() });` 4. Go through the workflow of initiating suggested edits, choosing topics, and changing topics. Try everything out! You can always re-run Step 2 to reset the whole workflow and see the initiation pieces again. 5. Note any issues relating to: ** Missing or incorrect translations ** Interface behaving strangely or looking weird ** When you select a topic, get results, then switch topics and switch back, you are supposed to get different results than you got the first time. We want to make sure that not all users who select "Music" get the same article suggestions. ** Poor topic results. This is important, especially because @Dyolf77_WMF noted in T242400 that results in the module looked different than the ones coming over the API. Please try out several different topics and think about whether the performance is better or worse than previous tests. 6. Try all of this on your mobile device. You can reset the workflow on desktop with Step 2 so that you can try it on mobile. Please post any issues or concerns as comments on this task. If you have to update translations, let us know when you've done that in Translatewiki so that @Catrope can update them manually before the next train runs.

It is time to test out topic matching in production. It is currently only available to users who run the code below to turn on the hidden preference. We want to have all test results by Monday, Jan 20 so we can plan to expose the feature to newcomers on Tuesday, Jan 21. Below are instructions for how to test. [X] Czech [x] Korean [] Vietnamese [x] Arabic 1. Go to the newcomer homepage in your wiki. 2. Reset the suggested edits workflow for your user. Do this by opening your browser tools (by right-clicking and choosing "Inspect") and running this in the console: `new mw.Api().saveOption('growthexperiments-homepage-suggestededits-activated', 0).done( function() { window.location.reload() });` 3. Enable topic matching by running this in the console: `new mw.Api().saveOption('growthexperiments-homepage-suggestededits-topics-enabled', 1).done( function() { window.location.reload() });` 4. Go through the workflow of initiating suggested edits, choosing topics, and changing topics. Try everything out! You can always re-run Step 2 to reset the whole workflow and see the initiation pieces again. 5. Note any issues relating to: ** Missing or incorrect translations ** Interface behaving strangely or looking weird ** When you select a topic, get results, then switch topics and switch back, you are supposed to get different results than you got the first time. We want to make sure that not all users who select "Music" get the same article suggestions. ** Poor topic results. This is important, especially because @Dyolf77_WMF noted in T242400 that results in the module looked different than the ones coming over the API. Please try out several different topics and think about whether the performance is better or worse than previous tests. 6. Try all of this on your mobile device. You can reset the workflow on desktop with Step 2 so that you can try it on mobile. Please post any issues or concerns as comments on this task. If you have to update translations, let us know when you've done that in Translatewiki so that @Catrope can update them manually before the next train runs.