@JKatzWMF We're putting together the Q2 goals and I wonder if it makes sense to run the demographics survey on logged in users (editors) in Q2. If we want to do that, we need the QuickSurvey to have the functionality to check for logging in/out status. I'm ready to bet that @Jdlrobson had made a phab task for that, but I can't find that. I can find T186737 (which is relevant I believe). For context: my request is related to Output 1.3 under Progressive Onboarding. Please note that on our end, we have a lot to do in Q2, so we're fine with it to run in Q3, but if the organization (Audiences specifically) needs the results of it soon to inform your planning, we should consider running it in Q2. :)

Current status:

• Privacy policy: currently working w/ Privacy now that we have a more concrete plan for the surveys
• QuickSurveys: added functionality complete but waiting on status of two possibly related bugs (T218243 and T220627)
• Potential for some preliminary insights: the reader demographics surveys (T203042) should provide some early insight into editor gender

TODO:

• finalize English version of question/answers
• determine languages to be included in surveys and coordinate translations
• work w/ communities to make sure no major concerns

work w/ communities to make sure no major concerns

Please remember to not distribute figures about gender diversity without correcting for selection bias and other demographic distortions, cf. Hill & Shaw 2013 https://meta.wikimedia.org/wiki/Research:Gender_gap

Please remember to not distribute figures about gender diversity without correcting for selection bias and other demographic distortions, cf. Hill & Shaw 2013 https://meta.wikimedia.org/wiki/Research:Gender_gap

@Nemo_bis -- yes, thank you for raising the point. That's one of our main aspects we're testing with these surveys. As you note, selection bias has been a large concern with past surveys. We're hoping that this survey will hopefully have less issues with selection bias or at least present a complementarry view into the data on editor gender because it is a single question (lower barrier to response) and we might be able to apply some debiasing techniques based on EventLogging and page view data that allow us to account for things like how many times a given respondent saw the survey before replying. At the end of the day, of course, we won't ever know the true numbers but having multiple ways of looking at them will hopefully help us understand how much uncertainty there is about them.

All: I will resolve this task as providing stats across many projects should ideally follow the recommendations in https://meta.wikimedia.org/wiki/Research:Surveys_on_the_gender_of_editors/Report#Recommendations .