In T428876#12056376, @DDeSouza wrote:

@soworu >7K responses. Response rate ~63%. I'm undeploying.

Query

SQL
SELECT
  CASE
    WHEN contains(event.surveyAnswers, 'mobile-app-awareness-2026-en-survey-yes') THEN 'yes'
    WHEN contains(event.surveyAnswers, 'mobile-app-awareness-2026-en-survey-no')  THEN 'no'
    ELSE 'other'
  END                                       AS response,
  count(*)                                  AS responses,
  count(DISTINCT event.surveySessionToken)  AS people
FROM event.quicksurveysresponses
WHERE event.surveyCodeName     = 'mobile-app-awareness-2026-en-survey'
  AND event.surveyQuestionLabel = 'mobile-app-awareness-2026-en-survey-q00'
GROUP BY 1
ORDER BY responses DESC

Returned

response	responses	people
yes	7532	7394
no	4471	4457

In T428876#12054043, @DDeSouza wrote:

@soworu I'm not monitoring the survey responses, but I may still have access to them via Superset, so I'll check. What number would you consider a sizeable amount?

Above 5,000 responses would be ideal.

@DDeSouza Hi. Checking-in on progress. If we've got a sizeable amount, we can close. Thanks

In T428876#12032363, @DDeSouza wrote:

@soworu Q06 and Q09?

In T428876#12032363, @DDeSouza wrote:

@soworu Q06 and Q09?

@DDeSouza Since we can't anchor options in Q06 and Q07, let's just turn off randomisation for those two.

In T428876#12029147, @DDeSouza wrote:

@soworu

Please review the survey at https://en.wikipedia.org/wiki/Wikimedia_Foundation?quicksurvey=mobile-app-awareness-2026-en-survey&uselang=en.

What needs change?

Thanks @DDeSouza, this is really helpful, as most of it works for me.

• Caps on selections: fine. The on-screen "select up to N" instruction is enough for what we need.
• Randomization (Q06, Q08, Q09): yes, let's keep them randomized. The one thing to watch is if any of those has a catch-all option ("None of these" / "Other" / "Don't know") that really ought to sit at the bottom. If so, flag it and we'll set just that question to fixed order instead.
• Q06 exclusive option: since we can't enforce it, let's make the exclusivity clear in the option wording itself, and I'll clean any conflicting selections (exclusive option picked alongside others) at the analysis stage. Workable.
• Open text in a multi-answer question: agreed it's worth testing rather than assuming; let's confirm in the pre-deployment.
• Privacy statement: your suggested wording works, let's use it as-is.
• And thanks for spelling out the pre-deployment approach.

@DDeSouza Yes, it is finished. Thanks for processing for pre-deploy.

@BCornwall, If that is the case, please do the as needed, subject to @Ottomata approval. Thanks.

SSH key: SHA256:9+15cZ0xKHi7PqAzF0LR1NXfsD5ex8PbiojwKfqoLSk soworu@wmf2559

Hi @SCherukuwada. Charlene confirmed that there's an MSA on file. According to her feedback

Hello Andre. This request emanated from the project we are running with Monsoon. I'm the project lead, and would be the approving party. The request is primarily limited to access to Google Search Console only.

Not valid anymore. Can be archived.

Project is no more valid. It can be archived. Sorry for responding so late.

This project was canceled in the context of the dissolution of the Community Engagement department. There are no plans defined as of now.

This project was canceled in the context of the dissolution of the Community Engagement department. There are no plans defined as of now.

This project was canceled in the context of the dissolution of the Community Engagement department. There are no plans defined as of now.

This project was canceled in the context of the dissolution of the Community Engagement department. There are no plans defined as of now.

Thanks for the prompt feedack. If that's the case, then all other are okay witout Kanuri. Thank you.

In T252705#6225588, @RobH wrote:

@soworu,

This has been pending feedback since May 26th regarding:

In T252705#6146379, @RLazarus wrote:

Hi Segun, thanks for the clear and complete request! I've granted you "restricted user" access for almost all those domains, which I think is the right level of access for your needs. If you need "full user," let me know and I'll upgrade you (or file another task, if you find out later).

Question for you: There is no KR.wikipedia, can you clarify whether you need access to (my best guesses) KO.wikipedia or KRC.wikipedia? That's the only item I haven't taken action on yet.

Please provide feedback so we can resolve this request, thank you!

In T252703#6152109, @Dzahn wrote:

@soworu I found the following comment in the Apache config of superset:

31         # Note: uid is used instead of cn since Superset needs the shell username to properly
32         # create users when they log in.

In turnilo's config i do not see this comment.

For many but not all users UID and CN are the same, but for you they are not.

I think this means you have to use "soworu-01" for superset but "SOworu" for turnilo.

In T252703#6152094, @Dzahn wrote:

@soworu Looks like it works now, i think i just saw you login in the log files, am i right?

In T252703#6152084, @Dzahn wrote:

@soworu Try again now, please. Looks like i forgot to add the -01 part when adding you the right group. Sorry about that.

In T252703#6152029, @Dzahn wrote:

Please try the following variations of the username including the capitalization:

soworu-01 and SOworu

In T252703#6142940, @Dzahn wrote:

@soworu Use the same user/password you used on https://wikitech.wikimedia.org when you created your account there.

In T252703#6137505, @Nuria wrote:

@soworu You will have superset and turnilo

This is all you need to access all data to be clear.

In T251523#6135269, @colewhite wrote:

Hi Segun!

Is it safe to assume you will need the same level of access to Analytics data as @ahemmer? T251123