Thank you for debugging this, Sergio! I am taking a look now.

I would support updating the we-1-8-mobile-account-menu experiment to show both permanent/temporary account creation rates.

Hi, I'm following up on a comment on patch 1253392. I don’t think patch 1253392 surfaced this error, because I can’t see a way in which those changes would have removed or changed $item['href']. Let me know if you have any other questions, thanks.

Re: the third AC, design okayed the changes via slack. Here's a link to the relevant thread. https://wikimedia.slack.com/archives/C02F2C8UUF4/p1774624224253229

Thanks for the follow-up, Elena and Amin. 🙏🏻

@Etonkovidova That is good to hear. Thanks for testing.

@Urbanecm_WMF Thanks for the feedback. I tried to clarify the acceptance criteria and look forward to discussing the task in backlog refinement. Please let me know if you'd like to share feedback via phabricator before then. I am concerned the way I wrote the AC is somewhat roundabout.

There is another task, phabricator.wikimedia.org/T416666, which involves the work on styling. This task is focused on logic.

Hi Elena, I apologize for missing your question last week. You can’t see the change in patch demo because TestKitchen is not available in patch demo. As Michael said, you should be able to view it at https://en.wikipedia.beta.wmcloud.org/wiki/Main_Page?mpo=we-1-8-mobile-account-menu:treatment, but beta appears to be down right now…. I’m unsure why.

Hi @AAlhazwani-WMF, I'm working on the implementation for temp accounts. I have a question similar to what I asked you in a comment on this task https://phabricator.wikimedia.org/T415648. Could you please confirm that users with temp accounts, as they are considered logged-out mobile users, should also see the "Create account" and "Log in" menu items on the hamburger menu?

Hi, I wanted to add the context that I already have deployment access, which was granted to me via this task. https://phabricator.wikimedia.org/T418221

@KStoller-WMF March 26th, 2026 and June 30th, 2026 sound fine to me. I added those dates to https://test-kitchen.wikimedia.org/experiment/we-1-8-mobile-account-menu.

I made a very bare-bones measurement plan and saved it in Growth Team's google drive. It can be seen here.

@KStoller-WMF I have a follow-up question. I'm adding this A/B test at https://test-kitchen.wikimedia.org/create-experiment. It requires start date and end date to be filled out before I can save the experiment. We still have TBA for both of those dates. Any sense of what dates we'll want the test to run? Thanks!

Hi @KStoller-WMF, I am good with bundling T415647 and T415648 together in one experiment. Thanks for clarifying.

Hi, I noticed that the task's "Requirements" section includes the phrase "See technical context @Michael shared in TICKET." Which ticket is this referring to? Thanks!

@thcipriani I looked and my request for Spiderpig-access is still pending. Could you please grant me access? Thanks!

@Aklapper I linked my LDAP account to my Phabricator account, and my 'LDAP User' account is now shown on my Phabricator profile. Thanks for catching that.

Hi @AAlhazwani-WMF, I wanted to clarify expectations for users who have temporary accounts. The task opens with "As a logged-out mobile web user." Would that group include users with temporary accounts? Or is the experience unchanged for temporary accounts? Please let me know, thanks. 🙏🏻

@Etonkovidova Thanks for the background context about T370239. I responded to your comment on T398428 as well.

Hi @Etonkovidova, thank you for flagging this. My understanding was that we want the Suggested Edits to accept custom inputs, because users might want to select a template from a different wikipedia. That is why Suggested Edits allows custom inputs, but Namespaces Control for T415288 does not. Please let me know if I am missing anything or misunderstood the scenario I mentioned.

Hi @Etonkovidova, I wanted to flag some unusual behavior related to this task. Today while I was pairing with Martin and working on my local master branch, which included this change, I saw an error when attempting to delete a namespace from Namespaces Control. The error message was "NULL value found, but an integer is required." I wasn't able to consistently reproduce the bug, and it may have been causing by forgetting to hard refresh after updating master. That being said, I wanted to highlight this scenario as one to test especially carefully during QA.

I wanted to clarify a change to the task. Previously, the task incorrectly said that users should be able to enter custom input. After testing on test.wikipedia.org, I realized that is not desired behavior. The task has since been updated.

Thanks for tagging me, @Urbanecm_WMF. I will take a look at this and get back to you.

Here are notes for how to do manual QA for this task. (I know the task isn't there yet, but I am including these notes for future QA.)
Scenario: No mentors on a wiki.

1. On a wiki that has no mentors, navigate to the Special:ApiSandbox page.
2. Select action=helppanelquestionposter.
3. For source, select "mentor-helppanel" from the dropdown.
4. Submit the request.
5. You should see an error that explains there are no mentors.

Done. Thanks, @DMburugu.

Hi @AAlhazwani-WMF, I made the requested change and it was straightforward. Here are screenshots of the change on desktop, in the mobile view, and zoomed in. After this I'll upload my changes to Gerrit. Thanks, let me know if anything looks off.

@AAlhazwani-WMF Sounds good. I will look into making the change. 🙏🏻

FYSA: Martin and I met today and agreed to split the associated gerrit patch, https://gerrit.wikimedia.org/r/c/mediawiki/extensions/GrowthExperiments/+/1199799, into multiple tasks. This task, T293454, will only include

Thank you, @Urbanecm. You're right that making the task more specific will make it easier for us to agree when the task is completed. That will also speed up the review process, which is good. What do you think of the current task? Also, do you like the idea of including "antigoals" in the task? In my experience, it can be helpful for preventing scope creep.

Hi @Urbanecm, could you please provide feedback on this task? Thanks.

I am closing this task. I have been convinced that it is not necessary.