Weekly updates:

• Met with Qualtrics rep for renewal discussion, should receive some quotes early next week
• CentralNotice: WMMX has finalized their survey revision from last Q and I've given approval to proceed :)

• No new updates this week, ThisDot are progressing on building multiple questions and I'll continue to be available to answer questions/test features as needed :)

Weekly updates:

• The survey opt-in is officially closed as of today, and the core survey will remain open over the weekend for any partial respondents who want to finish the survey
• CI metawiki page and my user page have been updated to inform any potential respondents who didn't see the opt-in message earlier that the data collection is complete
• Unsent automated reminders are canceled
• Next week, begin data cleaning and weighting :)

Weekly updates: no major updates this week :)

Weekly updates:

• Kicked off the QuickSurveys update work with ThisDot, who are now working on tool exploration and defining specifications for the scope and what can be implemented. Met with TSP today to discuss sampling possibilities, from first impressions list-based sampling and quotas are more difficult to implement, while more nuanced edit bins and bin probability targetting (rather than whole sample targetting) seems more feasible. Project epic can be followed here: T362640

Weekly updates:

• no major updates, will send final reminder to grantees next week and close out the survey on 25 April. After that, we start data cleaning/recoding, weight calculations, and analysis!

Adding a couple more scenarios for question paths in thinking about long-term development of the tool (these are, again, cool if possible but not required in this scope):

Possible scenarios (using safety survey as an example):

Closing this task. Community Growth will be working with CN admins for the rest of the FY, thus closing out the Community of Practice regular meetings.

Weekly updates:

• Began exploration of current data to prepare for recoding and digging into factor analysis methodology for motivation questions
• Continuing to track incoming data and response rates, they are lower on the largest wikis this year (except for EN which is on par with last survey) but higher among all smaller project groups
• Will send invites to recent grantees next week, which should be the last step of data collection

Weekly updates:

• No major updates this week, met with affiliate staff from WMCA to discuss surveying in Wikimedia, have a review for WMMX survey on CN next week

Updates for the last two weeks:

• Helped onboard Mobile Apps team user to basics of LimeSurvey
• Assisted Design Research on brainstorming on volunteer motivations/archetypes
• Reassigned one Qualtrics staff user account, and opened one LimeSurvey staff user account
• Assisted Movement Comms with question about how to assess proposals within their tool
• Inputted to review of data collection guidelines (requested by Legal)

Weekly updates:

• Community Insights is live and collecting data as of Wednesday! So far we have ~1800 responses, and a reminder email for those who opted in to be sent a link but haven't completed the survey yet is scheduled for 9 days after the opt-in (starting next Friday). I anticipate a small bump in responses over the weekend as well.
• Ongoing tasks in the short term are to continue communicating with editors who reach out and monitor the incoming data.

Weekly updates (apologies for the delay, final push this last week!)

• Launch announced in WMF Friday email via Movement Comms
• Translations are updated for all questions and messaging (we will be skipping new questions in SV, NL, HU; we may get a staff review on FI before tomorrow morning, and have received a staff review on BN!)
• Link relay emails and reminders are set up and all seems to be functioning (thanks to RDS folks for helping us to find issues and debug!); latin script has been removed from RTL languages in the invitation email to fix issues with plaintext formatting
• Added Invitation message meta page for a link to more languages at the end of the invitation email (eg. for Commons users, where we don't know their language setting so they all get an email in English, and all languages where we don't have a translation)
• Sample has been pulled and cleaned, updated on Research gitlab
• Language mapping for distribution complete
• Opt in and Opt out links generated

Weekly updates:

• Met about and finalized recommendation for survey tools
• Assisted Community Programs with brief survey review & Mobile Apps with setting up a LimeSurvey account

Weekly updates:

• Still waiting for ZH, PL, RU, AR, CS, IT and TH translations
• We have tested the EmailUser invitation sending with staff; it is working fine with LTR, but buggy with RTL languages due to issues with unicode plaintext for punctuation and much more when mixing RTL and LTR scripts (eg. when noting "Qualtrics" as the external survey tool for linking to their privacy policy, it flips half of the sentence to the beginning). It may make more sense to invite RTL wikis through Qualtrics emailing as it supports HTML. Alternative is to remove latin words from the text but accept that punctuation and alignment will be weird.
• We have scheduled the distribution to the 19th and 20th of March, as the March mediawiki_history table is due to be released next week (allowing for the most current possible sample, especially important for lower-activity active editors); sampling is scheduled for the 14th of March
• Community Insights meta page, end of survey page, and survey questionnaire page are updated
• I have begun setting up the opt-in automation (send survey link immediately to users who opt in) but am dependent on translations to finalize it

Weekly updates:

• Translations are underway (CA, ID, RO complete thus far) - target: March 7th
• Community Insights meta main page update is drafted (to be published next week), still to do: post survey form, make new end-of-survey landing page, and when we know the launch date post a banner/header to inform potential respondents of the dates and who is contacting them
• @YLiou_WMF and I are in conversation about how to best report aggregate survey data in knowledge gaps index data reporting scope

Weekly updates:

• No major updates;
  • Continuing work on survey tools decision-making with aim for a recommendation next week
  • CentralNotice Community of Practice met again (T341836) with aim to catalogue social and technical solutions to challenges CN admins face; I worked on drafting a surveys request proposal (here - private link) to help streamline CN survey requests and inform requesters of requirements

Weekly updates:

• I have been working on SWOTs for Qualtrics/LimeSurvey for decision-making for the next fiscal year (here - private link); will need to gain consensus from the team for next steps and then move forward a recommendation to Research management for the coming FY

Weekly updates (short week for me this week):

• Translation file is finally sent out for review! (anticipated ~2 weeks turnover)
  • Update here: We will be missing updated translations for NL, BN, SV, HU, & FI. Review section has been shortened to stay within budget.
• Motivations for contributing items have been reviewed by people from Design Research, Product Design, and Community Programs; we are converting the "select all" into importance scales to reduce cognitive load
• KCV has started testing EmailUser distribution, I'll be asking Research team and others for volunteers to help us test whether everything is functioning
• Next up: update the Community Insights wiki page, set up the messaging relay (opt-in to send link)

Weekly updates:

• Met with CentralNotice admins on Friday as part of Talking 2024. They noted feeling a large amount of responsibility as volunteers for the wide reach of CentralNotice and that a lack of written guidelines from WMF makes this more difficult; shared that I will be contacting them with a proposal for updating survey guidelines (which will hopefully reduce at least one point of pressure on admins)

Weekly updates: No major updates, continuing to move forward :)

• Confirmed budget for translation, will need to update translation doc to reduce redundancies (eg. repeating agreement scales, country lists) to not over-inflate our word count
• Obtained Staff permission from ca@ for using EmailUser API at high sending rates
• Refining the motivations for contribution categories based on recent work by Design Research and past literature
• Consulted with Community Growth about age distributions by region in the CI data, and dug back into some 2020 data add insight to an AP question

Weekly updates:

• No major updates; the CN Community of Practice met again (T341836) (notes - private link), and I'll be attending the Talking:2024 meeting with CN admins next Friday

Weekly updates: No major updates for this week, just moving along towards distribution :)

• Translation document is 99% ready (private link here); to be submitted for translation early next week
• We will be missing BN, HI, KO, TH, SV, and FI translations with Movement Comms - since new translations are minor and the primary goal is to verify translations are legible in wiki-language, I suggest we ask staff and potentially community members for help in reviewing these

Weekly updates:

• No new updates this week. Next week, the Central Notice Community of Practice (T341836) will meet again after an end-of-year hiatus, and there is a plan to meet with CN admins the following week as part of Talking:2024.

Weekly updates:

• Privacy statement received (here)
• We will be adding a motivation for contributing question based on past affiliate surveys (see question here), this will require translations
• Shared additional analyses on age to team
• Following T355449 (aligning to new Google email standards) as it directly impacts our distribution via EmailUser
• Still in progress: setting up messaging and questionnaire translation documents for review (and translation of any new messaging/questions)

Hi @jhathaway -- is EmailUser within the scope of this ticket (I assume yes as it's as far as I can tell using Mediawiki mailer and the wikimedia.org domain)?

Weekly updates:

• Qualtrics use-cases shared for 2024 (private link)

Weekly updates:

• Privacy statement request submitted to Legal, added estimated distribution for March on Movement Comms calendar
• Obsolete questions removed in survey schedule
• Seem to have figured out a way to alphabetically sort response options across translations on Qualtrics! Temporary documentation here (private link), it appears to be working in Latin and Cyrillic scripts in preview mode, will need to check on other scripts.
• In progress: setting up messaging and questionnaire translation documents for review

Weekly updates:

• 2022 response rates and new wikis list for sampling strata (T354510) and distribution shared (T354512); met with @KCVelaga_WMF to kick off this work
• Variable names and skip patterns updated in Qualtrics
• Added new simple Wikimedia theme on Qualtrics for accessibility and branding consistency
• Setup and numeric conversion R code written for YoY data

Weekly updates: No major updates this week; goals set for the quarter.

Weekly updates: no updates this week, assisted on CentralNotice with WUGN annual recruitment survey review

Weekly update: data cleanup is complete! CI data is now in a software-neutral format (CSV) with a codebook documenting all variables, types, question wording, wording changes, user notes, recode sources, and year availability. This standardization will also help to speed up data processing once the 2024 survey is complete. Codebook is available here (private link).

Weekly updates: no major updates, provided feedback to WUGN editor recruitment survey request on CentralNotice and received feedback from @Pablo on the survey support deck

Weekly update: data cleanup is 99.9% done!

Weekly update: no major updates, continued progress on data cleanup - hoping to be done with this portion of the work by end of next week

Weekly updates: no major updates, began drafting an outline for staff survey guidance as a deck - comments for things the team found out and wished they had known very welcome!

Weekly update

Confirming @Jdrewniak we should be done with all surveys by December 15th. Thank you for letting us know about this!

Weekly updates: no major updates this week

Weekly update: no major updates, making substantial progress on cleaning out data (finished with core sentiment variables, now moving to demographics and constructs). Provided 2022 analysis on knowing where to find help for major wikis to product analytics/T&SP to inform their research on incident reporting. Next goals are: finish cleaning and renaming, ensure we have everything we need from SPSS before end-of-month subscription cancelation, output a codebook documenting each wave of the survey and questions/variables, and then move to survey structure on Qualtrics.

Weekly updates: no major updates on Q2 goal; provided feedback to WM Chile for their community survey via CentralNotice

Weekly updates: no major updates, but returned to making progress on cleaning data now that Readers survey is largely ready

Frwiki:

I can't quite figure out what the issue is here, as https://fr.wikipedia.org/wiki/MediaWiki:Reader-demographics-2-survey-description and https://fr.wikipedia.org/wiki/MediaWiki:Reader-demographics-2-survey-question both exist and are correct, and look correct on the commit. Will continue to look further.

I don't know what is wrong. I'm able to load another survey on the wiki. The survey doesn't show on the extension data which indicates a configuration issue but configuration looks good. Maybe something went wrong during deployment.

Thank you so much @DDeSouza !

Weekly updates: no major updates, focus on Readers survey this past week

Weekly update: no major updates on Q2 goal as we focus on deploying Readers survey; provided feedback to WMDE for their community survey

@YLiou_WMF and I provided feedback on the survey script and talked through decisions with Martin; we suggested deploying separate links to different edit bins of users in order to be able to weight the data to edit bins, but ultimately it is up to their team how their want to run the survey. Once a page is made on wiki describing their privacy practices and the survey tool they're using, we can approve this survey to deploy on CentralNotice. They may come back to us with finalizations, but we can consider this task closed :)

Hi @DDeSouza, I think I have all the links set up for the 23 language QuickSurveys! Would it be possible to deploy at 0 coverage this week so we can make sure everything looks right? I believe our hopeful target date for data collection next Monday, the 13th.

Hi @leila, thanks for this -- for now I think the best way would be to route them to email surveys@ and ask them to share as much context as they can:

• their survey project goal
• timeline
• their project meta/wiki page
• the survey draft ideally in a google document where we can comment
• how they plan to collect responses
• whether they've made a privacy statement

Weekly update: No updates on Q2 goal this week, onboarded Wikimania '24 organizers to LimeSurvey

Weekly update: No major updates, making substantial progress in cleaning out redundant variables from the year-over-year CI dataset

Updated with all existing translations, see doc for comments; awaiting HU translation, as well as FA, ZH-S, NL from Qualtrics.

Hi @YLiou_WMF ! Checking on 2 things as I get into T346903 this week:

1. Did we get a translation of the privacy policy link statement for QuickSurvey? I can't seem to find it in the translation links. Ie. this text https://en.wikipedia.org/wiki/MediaWiki:Reader-demographics-2-survey-privacy-policy
2. Do we have a confirmation for which languages are done with translation? Eg. Czech and Ukrainian seem to be incomplete in the links above

Edit: here are the languages I found to be incomplete (new translations not added in original doc; may be in a separate file?)

• CS
• ES
• FR
• HE
• HU
• PL
• UK

Weekly update: No updates this week

Weekly update: No major goal updates this week
Broader project updates:

• Presented 2022 overview data to senior leadership to help inform on "who are active editors"
• Ran breakout data for 2022 LAC region

Project is scoped here (private link). Moving to implementation in Q2 (T347589) :)

Needed changes and potential fixes to implement are scoped here (private link). This quarterly goal task is done; moving to implementation in Q2 (T347594) :).