The experiment is finally running properly. QA itself is happening in a different task.

This has been restarted and should be working smoothly.

Looking into it, I don't think anything is wrong with our tests. It just seems that sometimes core is forgetting the correct token, for whatever reason. postWithToken in resources/src/mediawiki.api/index.js even has retry code for specifically that:

This should be resolved by switching to the underlying component to MultiselectLookup instead of homegrown things. See T400812.

The issues here have fully stopped, the last one was on February 25th. I think the way we achieved is by disabling GrowthExperiments on closed wikis.

I think the issues here have been fixed by switching to a MultiselectLookup in T400812.

This was done in the associated change.

Let's move this back to doing. We'll analyze it in GrowthBook after backporting two changes today and restarting the data collection tomorrow.

This is something that needs to happen in the pipeline. Moving it to tracking, because it also affects what images are presented in the Growth Add-an-Image newcomer task.

Today, @mpopov, @MNeisler, @Sgs and I met to look into how implement the metrics with the new GrowthBook tool

While the dependencies are not merged yet, let's move forward with creating this anyway with the assumption that the dependency is not going to be fundamentally blocked.

This keeps failing a lot. Still no idea why. Let's skip it for now.

https://integration.wikimedia.org/ci/job/quibble-vendor-mysql-php83-selenium/39702/console seems to be another instance of this.

In T421968#11795051, @DLynch wrote:

This is specifically about "Add a link (structured task)", not "add links between articles".

[...]

What's not supported is:

• Weight of underlinked articles; I'm not actually sure what this applies to -- it doesn't seem to map to any of the API parameters, so I think it might be a configuration for how likely it is to actually show up on the user homepage?

Let's move this into the sprint, because I'm defacto already actively working on this, just so far I labeled that work as part of T419916: [V1 experiment release] Redesign mobile web account creation form following Codex guidelines, but now maybe it can be more accurately done as part of this task here.

@Elisapoly Thank you!

In T419395#11788928, @KStoller-WMF wrote:

Thanks for the feedback, @A_smart_kitten !

I'm also not completely sure right now about hard-coding some of these requirements into MediaWiki core (as it currently seems like might be happening, with apologies if I am incorrect) — e.g. how can we say that there aren't third-party wikis out there that encourage usernames that (e.g.) would completely go against the English Wikipedia's policies?

Short term we are only planning to A/B test this on English Wikipedia.
Long-term we hope to find language that is more general and can ideally work for any WMF-maintained wiki.

I'm not sure what the best strategy would be for that once we consider a broader release.

• Remove that string about usernames needing to represent an individual and not an organization? (And let enwiki override the string and add that in if they think that's necessary for this succinct summary?)
• Do we only enable this on wikis with GrowthExperiments?
• Do we allow communities to adjust this via Community Configuration?
• Something else?

Let us know if you have thoughts on how to approach this once we are ready for a wider rollout.
Or maybe @Urbanecm_WMF has a recommendation?

I haven't heard about that coming up again in the last years. Let's close it. If you still notice this happening, please reopen!

Please also add our tags when there are issues with our code.

In T416666#11782469, @Sgs wrote:

In T416666#11782171, @Michael wrote:

I think we talked about this error-message at the top: it is fine to remain as a block-styled error message. Only the ones directly associated with an input should change to the inline style.

Ack. Also, for clarity, this change can be released as regular improvement, not platform specific, and it is not part of any create account experiment right?

QA Note: I don't know how much QA is actually needed here. This should have been only cleaning up code and config options that are no longer used.