In T256126#6801220, @Urbanecm_WMF wrote:

• They want to link https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide/da#Editing_images_and_other_media_files in the help panel for "Inserting images using the visual editor", but in extra links, https://da.wikipedia.org/wiki/Hjælp:Billeder is mentioned for "how to add images".

Because I haven't triple checked the links. Hjælp:Billeder is about adding images using wikitext, and we encourage VE.

I picked the links myself.

• Is it wise to link mediawiki.org page from the interface? Won't that guide newcomers away to a different project, leaving them lost for good? @MMiller_WMF might have some opinions about that

Since we don't have a proper link on da.wp, we only can rely on other existing resources. IT is suboptimal, but I hope that communities will react to this.

What should I add as a description to those pages? Just the page title?

Just the pages titles, thanks.

In T256126#6801263, @Trizek-WMF wrote:

In T256126#6801220, @Urbanecm_WMF wrote:

• "Help pages" in the "Help desk" section lists several pages that should be linked from the help panel. The configuration needs both title and text that should be displayed. That's similar to [[Title|Description text]] in wikitext. What should I add as a description to those pages? Just the page title?

Just the pages titles, thanks.

And how should I deal with the mediawiki.org pages, when the title is not in Danish?

In T256126#6801278, @Urbanecm_WMF wrote:

And how should I deal with the mediawiki.org pages, when the title is not in Danish?

Good point. I used existing translations from translatewiki, if they match at 100%. Otherwise, I google translated the labels.

The tools will first be deployed only for people who wish to enable them in their preferences so that they can check and update translations.

In T256126#6801307, @Trizek-WMF wrote:

In T256126#6801278, @Urbanecm_WMF wrote:

And how should I deal with the mediawiki.org pages, when the title is not in Danish?

Good point. I used existing translations from translatewiki, if they match at 100%. Otherwise, I google translated the labels.

The tools will first be deployed only for people who wish to enable them in their preferences so that they can check and update translations.

I'm not sure I understand your message properly. Can you say it in different words, please?

1. look if the translation already exists on translatewiki. Example for 'add image' -> search -> find -> we use "Tilføj billede"
2. If I don't find anything, I use Google translate
3. you add the translations to your patch
4. you deploy
5. I inform communities about the deployment
6. they check the translations
7. we open the gates to newcomers

I will update the translations tomorrow.

Thanks @Trizek-WMF. I was under the impression that I'm supposed to look for the translations somehow. I'll wait for your translations then :).

NewcomerTasks.json prepared at https://da.wikipedia.org/wiki/Bruger:Martin_Urbanec_(WMF)/NewcomerTasks.json, as I can't edit NS_MEDIAWIKI from my WMF account. @Tgr: Would you please review and move if it looks good to you?

Also the config patch should now be ready. Moving to CR column. Once CR'ed, please move back to In progress.

In T256126#6802177, @Urbanecm_WMF wrote:

NewcomerTasks.json prepared at https://da.wikipedia.org/wiki/Bruger:Martin_Urbanec_(WMF)/NewcomerTasks.json, as I can't edit NS_MEDIAWIKI from my WMF account. @Tgr: Would you please review and move if it looks good to you?

Done. I assume the learn more link for the update type was omitted intentionally, let me know if I should add it though.

In T256126#6801307, @Trizek-WMF wrote:

[...]
The tools will first be deployed only for people who wish to enable them in their preferences so that they can check and update translations.

I didn't see this super-important information in the description, so I added it there. What should happen with welcome survey? Should we enable it for newcomers as we do on other wikis, or leave it accessible through Special:WelcomeSurvey only for experienced users for now?

@Urbanecm_WMF -- good question. The welcome survey should only be available by going to the URL. It should not go to anyone by default at this stage.

In T256126#6802607, @Tgr wrote:

Done. I assume the learn more link for the update type was omitted intentionally, let me know if I should add it though.

Can you please add it? https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide/da

When the features will be deployed?

In T256126#6811281, @Trizek-WMF wrote:

Can you please add it? https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide/da

Done.

Thanks @Tgr!

When the features will be deployed?

That depends... The translation of special pages will be in production with wmf.30, which is scheduled to be deployed this Thursday (but wmf.29, the version we should currently be on, is still blocked, see T271343). I can't predict when will we be on wmf.30. If special page translations aren't a blocker, we can do it any time.

Change 661419 merged by jenkins-bot:
[operations/mediawiki-config@master] Enable GrowthExperiments at dawiki

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

Mentioned in SAL (#wikimedia-operations) [2021-02-08T19:17:11Z] <urbanecm@deploy1001> Synchronized wmf-config/InitialiseSettings.php: 3f39eefaa4c0dabfbc5b03fdc1b12e48913089bd: Enable GrowthExperiments at dawiki (T256126) (duration: 01m 05s)

Mentioned in SAL (#wikimedia-operations) [2021-02-08T19:18:34Z] <urbanecm@deploy1001> Synchronized dblists/growthexperiments.dblist: 3f39eefaa4c0dabfbc5b03fdc1b12e48913089bd: Enable GrowthExperiments at dawiki (T256126; 2/3) (duration: 01m 03s)

Mentioned in SAL (#wikimedia-operations) [2021-02-08T19:20:15Z] <urbanecm@deploy1001> Synchronized wmf-config/config/dawiki.yaml: 3f39eefaa4c0dabfbc5b03fdc1b12e48913089bd: Enable GrowthExperiments at dawiki (T256126; 3/3) (duration: 01m 04s)

Per today meeting, I enabled the features on dawiki today. It will be communicated to the community when the translations are ready (whenever T271344: 1.36.0-wmf.30 deployment blockers is resolved).

Moving to QA, as I would like to make sure the features work as expected, and that they are not deployed to newcomers yet. I triple checked the config I deployed, but just in case, it's worth checking.

In T256126#6812510, @Urbanecm_WMF wrote:

Per today meeting, I enabled the features on dawiki today. It will be communicated to the community when the translations are ready (whenever T271344: 1.36.0-wmf.30 deployment blockers is resolved).

Moving to QA, as I would like to make sure the features work as expected, and that they are not deployed to newcomers yet. I triple checked the config I deployed, but just in case, it's worth checking.

Thanks, @Urbanecm_WMF - I appreciate it very much!
I checked - all looks deployed as per the task specifications. For documenting and for @MMiller_WMF's additional review, below is the summary of what is not present (correct behavior) and I highlighted what I found kind of unexpected:

• new accounts do not get Welcome survey
• Homepage is enabled only via Preferences, but some account upon creation have a prompt (on a page, not a popup) to enable Homepage
• the Help panel is not enabled for new accounts
• newcomers after enabling Homepage do not have Mentorship module present (at least, it was the case for two new accounts that I created)
• many translations are not done yet
• the aliases, e.g. Special:Homepage -> Speciel:Hjemmeside cannot be found when typed in the search box

Thanks @Etonkovidova! I'm wondering what "some account upon creation have a prompt (on a page, not a popup) to enable Homepage" refers to? I'm not sure if that's right behavior.

@Trizek-WMF

• I can't visit the the welcome survey using special:WelcomeSurvey. I'm redirected to the wiki main page.

Special:WelcomeSurvey?_group=exp2_target_specialpage works on dawikii. I guess for just Special:WelcomeSurvey to work, there should be some aliases created.

@Etonkovidova The aliases merely change the URL itself, not the functionality of the feature. Apparently 'dawiki' => [ 'exp2_target_specialpage' => [ 'range' => 'x' ], 'exp2_target_popup' => [ 'range' => 'x' ] ], is not the right config :-). I asked in engineering slack channel what is the correct config, as the docs in extension.json aren't especially helpful on this topic :/.

Yeah the documentation of $wgWelcomeSurveyExperimentalGroups could be improved. x basically disables that survey type (and the only survey type we are still using is exp2_target_specialpage; popups didn't test well and the rest was just A/B testing byproducts. The relevant code is WelcomeSurvey::getGroup(). That's used both for registrations and when visiting the special page (unless there's an URL or user settings override). So there isn't really any way to make it work without the URL parameter.

I see. So, the question now is: Do we want it to work w/o the query parameter? If so, we will need to create a task and work on that separately from the deployment. @MMiller_WMF and @Trizek-WMF, this is probably a question for you.

@Urbanecm_WMF -- let's not do extra work to make it work without the query parameter. Here's the reason: since the community members will only be able to access the welcome survey from its URL (and therefore would have to copy/paste it from @Trizek-WMF's instructions), it won't matter whether the URL they copy/paste is short or long. So it's fine for them to also copy/paste the query parameter part if they want to test the welcome survey.

Well, I would prefer to tell communities to copy Special:WelcomeSurvey instead of Special:WelcomeSurvey?_group=exp2_target_specialpage.

Can we fix it for future deployments?

In T256126#6818383, @Trizek-WMF wrote:

Well, I would prefer to tell communities to copy Special:WelcomeSurvey instead of Special:WelcomeSurvey?_group=exp2_target_specialpage.

I would probably say "click here", but I get your point.

Can we fix it for future deployments?

Well, we can certainly make a task for it :-).

Should be pretty straightforward, just allow to pass in a default value when calling WelcomeSurvey::getGroup() so the fallback order would be URL -> user preference -> default -> roll the dice.

Since I'm trying to make a workable short wikilink including the parameter since 10 minutes: T274368: On wikis trying the Growth tools, have Special:WelcomeSurvey working without parameters. :)

The community has been informed about the tools and the forthcoming deployment. The deployment to newcomers would happen starting on Feb. 24.

Moving to QA - will do additional check after deployment to newcomers.

@MMiller_WMF @Trizek-WMF I just noticed that there are very few copyedit tasks (in all topics) available for Danish Wikipedia, and few of links tasks available for some topics. See the list below:

Is there anything we should do with this?

Skabelon:Oprydning is a possible alternative, but only has 323 articles linked ATM. I continue to look at better alternatives while you add this template to the configuration.

Also, nice script! Can you document and share it?

In T256126#6838434, @Trizek-WMF wrote:

Skabelon:Oprydning is a possible alternative, but only has 323 articles linked ATM. I continue to look at better alternatives while you add this template to the configuration.

Also, nice script! Can you document and share it?

That script is documented at https://wikitech.wikimedia.org/wiki/GrowthExperiments_setup, which is the page I'm using for setting GrowthExperiments up, and is available in the GrowthExperiments git repository. Sadly, it currently requires production access (restricted or above) to run it. We can probably expose those numbers via an API and publish it on a toolforge tool if you think that's useful (or, via a special page on each wiki).

In T256126#6838434, @Trizek-WMF wrote:

Skabelon:Oprydning is a possible alternative, but only has 323 articles linked ATM. I continue to look at better alternatives while you add this template to the configuration.

Was added to config.

@Trizek-WMF It is better now, through we still have 0-tasks topics:

I don't see any other template that would fit the task. I will ask communities about it.

Thank you for the information about the script. Getting access is a bit overkill for the need I have. :)

In T256126#6840816, @Trizek-WMF wrote:

I don't see any other template that would fit the task. I will ask communities about it.

Thanks!

Thank you for the information about the script. Getting access is a bit overkill for the need I have. :)

Yeah, sounds so :). Filled T275132 to expose those useful numbers in some more accessible way (perhaps a special page).

In T256126#6814576, @Urbanecm_WMF wrote:

Thanks @Etonkovidova! I'm wondering what "some account upon creation have a prompt (on a page, not a popup) to enable Homepage" refers to? I'm not sure if that's right behavior.

I observed the same behavior on thwiki where Homepage is in silent mode. After a new account is created, there is a landing page saying "you can enable Homepage via Preferences", that's all. It seems ok for the silent mode though.

Unfortunately, I do not have a screenshot available and could not reproduce the issue with two newly created accounts.

In T256126#6858724, @Etonkovidova wrote:

In T256126#6814576, @Urbanecm_WMF wrote:

Thanks @Etonkovidova! I'm wondering what "some account upon creation have a prompt (on a page, not a popup) to enable Homepage" refers to? I'm not sure if that's right behavior.

I observed the same behavior on thwiki where Homepage is in silent mode. After a new account is created, there is a landing page saying "you can enable Homepage via Preferences", that's all. It seems ok for the silent mode though.

Unfortunately, I do not have a screenshot available and could not reproduce the issue with two newly created accounts.

Do you mean this one? If so, this happens every time you view Special:Homepage manually, to give you an explanation of why it doesn't work. This page shouldn't be reachable from the registration process through.

Would T269847: Automatically enable the Homepage when a logged-in user visits [[Special:Homepage]] help there?

In T256126#6864253, @Trizek-WMF wrote:

Would T269847: Automatically enable the Homepage when a logged-in user visits [[Special:Homepage]] help there?

It would fix the issue, but I don't think it's a big issue. Easier thing might be linking https://www.mediawiki.org/wiki/Help:Growth/Tools/Enable_the_Homepage from the "not enabled" messge :)

Change 667570 had a related patch set uploaded (by Urbanecm; owner: Urbanecm):
[operations/mediawiki-config@master] Deploy Growth features to newcomers on da.wikipedia

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

In T256126#6868965, @Urbanecm_WMF wrote:

Easier thing might be linking https://www.mediawiki.org/wiki/Help:Growth/Tools/Enable_the_Homepage from the "not enabled" messge :)

Allow me to disagree: going to the talk page leads to a multiple step process to follow on a very unknown environment. It would at best discourage people from enabling the homepage or, at worst, lead people to quit because the tool is too complicated.

In T256126#6870564, @Trizek-WMF wrote:

In T256126#6868965, @Urbanecm_WMF wrote:

Easier thing might be linking https://www.mediawiki.org/wiki/Help:Growth/Tools/Enable_the_Homepage from the "not enabled" messge :)

Allow me to disagree: going to the talk page leads to a multiple step process to follow on a very unknown environment. It would at best discourage people from enabling the homepage or, at worst, lead people to quit because the tool is too complicated.

Interesting way how to look at it, didn't think about it. I think you have a point.

We can change the configuration for this wiki: 80% of newcomers to get the features.

Mentioned in SAL (#wikimedia-operations) [2021-03-03T19:40:26Z] <urbanecm@deploy1002> Synchronized wmf-config/InitialiseSettings.php: 7acb37c9b89d192bafc3b54adc33b569b3cea869: dawiki: Deploy Growth features to newcomers (T256126) (duration: 01m 09s)

In T256126#6880385, @Trizek-WMF wrote:

We can change the configuration for this wiki: 80% of newcomers to get the features.

Done!

@Urbanecm_WMF according to https://phabricator.wikimedia.org/T275908#6872093 - dawiki (without Mentorship module) should fall back to Help panel? I didn't see Help panel present there.

• Help panel not enabled by default for new users who get Homepage automatically enabled.
• the Help panel is not present on normal pages in editing mode
• the Help panel is not present for SE articles
• the option "Enable the editor help panel" is present in Preferences but does not have any effect if it's checked.

In T256126#6894407, @Etonkovidova wrote:

@Urbanecm_WMF according to https://phabricator.wikimedia.org/T275908#6872093 - dawiki (without Mentorship module) should fall back to Help panel? I didn't see Help panel present there.

Thanks for spotting this. Uploaded a fixing patch in the other task.

In T256126#6894755, @Urbanecm_WMF wrote:

In T256126#6894407, @Etonkovidova wrote:

@Urbanecm_WMF according to https://phabricator.wikimedia.org/T275908#6872093 - dawiki (without Mentorship module) should fall back to Help panel? I didn't see Help panel present there.

Thanks for spotting this. Uploaded a fixing patch in the other task.

Re-checked - all works (more details in https://phabricator.wikimedia.org/T275908#6898068)

Moving to PM review - all seem to be in place. Mentorship is not present according to the dawiki specific configuration.

@Urbanecm_WMF - there seem to be some incorrect redirects

The steps to reproduce the issue

• copy paste either Special:Homepage or Speciel:Hjemmeside in the Search box
• click on the search icon (the magnifying glass), the WelcomeSurvey page will be displayed with the url https://da.wikipedia.org/wiki/Speciel:Hjemmeside

If we don't do T250243: Scale: translation of aliases soon, we should probably fix the deployment task template so the special names are in the same order as in the alias file. Having to permute them every time one switches between the task and the code is error-prone.

Change 667570 abandoned by Urbanecm:
[operations/mediawiki-config@master] Deploy Growth features to newcomers on da.wikipedia

Reason:
not needed anymore

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