Change Details

We aim to distribute the biennial [[https://meta.wikimedia.org/wiki/Community_Insights | Community Insights survey]] of active editors across Wikimedia projects in April 2026. This task will serve as the Epic for the project to track various task components and the overall scope. Substantial changes: * We will be using LimeSurvey instead of Qualtrics * We will be using a single-email opt-in rather than double-email opt-in ====Set-up & Distribution==== [x] Review and revise questionnaire ([[ https://meta.wikimedia.org/wiki/Community_Insights/2026_Survey_Questions | Final ]]) ** Request stakeholder input for new questions - we do not want to substantially increase the length of the survey, but we should ask questions relevant to strategic or product initiatives which are likely to gain reliable and actionable data from the survey ** Remove questions that are no longer relevant [x] Finalize questionnaire text, including email invitation copy ([[ https://meta.wikimedia.org/wiki/Community_Insights/2026_Invitation | Final email copy ]]) [x] Send new questions and copy for translation [x] Scope multilingual and stratified sample process for LimeSurvey - should we use separate surveys for all languages, or use one survey? Ensure that we are able to maintain data integrity (subsamples, bins) and question localization (e.g. demographics) for whichever route we choose. ** (Decision: One survey with all languages, using a code system for strata weights) [x] Decide whether we want a method to remind participants to complete the survey ** (Decision: no reminder method; response rates appear to be on par with past years) [x] Program the survey, QA [x] Update metawiki page for the 2026 survey [x] Request privacy statement [x] Draw sample of qualified participants to contact at release of newest mariadb dataset (April 2026) [x] Configure EmailUser API and survey links for invitations; test and QA [x] Send out invitations! (Target: mid-to-late April 2026, depending on editor dataset update) ** (Sent 16 April 2026) ====Data Cleaning & Documentation==== [] Close survey (Target: 7 May EOD; may keep it open a bit longer as responses are still coming in at ~5-10 per day; ideally we want to drop to 0-2 daily) [] Update metawiki pages to inform community members and potential respondents that the survey is closed [] Clean responses (duplicates, straight-lining) [] Calculate weights and response rates [] Recode YoY questions to align with past questions/variables [] Append to previous Community Insights datasets for YoY analyses [] Update Community Insights codebook [] Update gitlab for sampling and distribution code ====Analysis==== To be updated when we get to this stage.

We aim to distribute the biennial [[https://meta.wikimedia.org/wiki/Community_Insights | Community Insights survey]] of active editors across Wikimedia projects in April 2026. This task will serve as the Epic for the project to track various task components and the overall scope. Substantial changes: * We will be using LimeSurvey instead of Qualtrics * We will be using a single-email opt-in rather than double-email opt-in ====Set-up & Distribution==== [x] Review and revise questionnaireaire ([[ https://meta.wikimedia.org/wiki/Community_Insights/2026_Survey_Questions | Final ]]) ** Request stakeholder input for new questions - we do not want to substantially increase the length of the survey, but we should ask questions relevant to strategic or product initiatives which are likely to gain reliable and actionable data from the survey ** Remove questions that are no longer relevant [x] Finalize questionnaire text, including email invitation copy ([[ https://meta.wikimedia.org/wiki/Community_Insights/2026_Invitation | Final email copy ]]) [x] Send new questions and copy for translation [x] Scope multilingual and stratified sample process for LimeSurvey - should we use separate surveys for all languages, or use one survey? Ensure that we are able to maintain data integrity (subsamples, bins) and question localization (e.g. demographics) for whichever route we choose. ** (Decision: One survey with all languages, using a code system for strata weights) [x] Decide whether we want a method to remind participants to complete the survey ** (Decision: no reminder method; response rates appear to be on par with past years) [x] Program the survey, QA [x] Update metawiki page for the 2026 survey [x] Request privacy statement [x] Draw sample of qualified participants to contact at release of newest mariadb dataset (April 2026) [x] Configure EmailUser API and survey links for invitations; test and QA [x] Send out invitations! (Target: mid-to-late April 2026, depending on editor dataset update) ** (Sent 16 April 2026) ====Analysis and reportingData Cleaning & Documentation==== [] Tasks for data cleaning,Close survey (Target: 7 May EOD; weighting,may keep it open a bit longer as responses are still coming in at ~5-10 per day; analysiideally we want to drop to 0-2 daily) [] Update metawiki pages to inform community members and potential respondents that the survey is closed [] Clean responses (duplicates, and reporting to be updated here as project progressesstraight-lining) [] Calculate weights and response rates [] Recode YoY questions to align with past questions/variables [] Append to previous Community Insights datasets for YoY analyses [] Update Community Insights codebook [] Update gitlab for sampling and distribution code ====Analysis==== To be updated when we get to this stage.