==October 20 Update==
Thank you all for your contributions and for the continuing incredible interest in this project! At this point, I believe that the project is closed on the Outreachy site. If you have completed a microtask for this project, just make sure that I can view it (using my email mraish@gmail.com). If you've shared it with me inside of the Google Docs interface, or left a link here on the task, I will have received an email notification and I will review it.
Unfortunately, due to the volume of submissions, I cannot acknowledge receipt of all microtask submissions—I've gotten too many and I'm the only person handling the applications for the moment. I hope you can understand.
Applicants with a contribution should [[ https://www.outreachy.org/docs/applicant/#make-contributions | record them here ]].
If you would still like to contribute to Outreachy, I encourage you to [[ https://www.outreachy.org/apply/project-selection/ | contribute to the other projects listed here ]]. Unfortunately, this project is currently closed for contributions.
Thank you!
===ALL SUBMISSIONS DUE BY END OF THE WEEK (OCT 14)===
Hi all, I've learned that some of you have been working on your microtask submissions and haven't yet had a chance to submit them. I'm sorry for prematurely closing this task, and I apologize to anyone who felt that they weren't given enough time to finish their work. In that spirit, I ask that any applicants still interested in submitting materials please do so by the end of the current work week; i.e., by Saturday October 14.
As viewers of this task can observe, this project has generated a lot of applicant interest. Thank you for your patience with me during this process.
===PROJECT CLOSED FOR APPLICATIONS, OCT 10 UPDATE===
Hi all, thank you for the incredible interest in this project! We have received a large volume of applications, and we will be reviewing and contacting applicants over the next week. I wish that we had the capacity to host everyone who applied. So, stay tuned if you have shared your microtask with me, and my team will be in contact with selected applicants in the next 7 days. Thank you!
IMPORTANT: Make sure to read the [Outreachy participant instructions](https://www.mediawiki.org/wiki/Outreachy/Participants) and [communication guidelines](https://www.mediawiki.org/wiki/New_Developers/Communication_tips) thoroughly before commenting on this task. This space is for project-specific questions, so avoid asking questions about getting started, setting up Gerrit, etc. When in doubt, ask your question on [Zulip](https://www.mediawiki.org/wiki/Outreach_programs/Zulip) first!
===Brief summary
We are looking for an intern who can help us conceive, write, build and administer, and analyze a survey that will help us better understand those who edit and use translation to contribute across different language versions of Wikipedia. The intern will participate in all stages of research, from meeting with stakeholders to decide what questions to ask, all the way through data collection, analysis, and composition of a research report.
===Skills required
Design research, research, survey design, project management, knowledge of general language/culture topics, data analysis and presentation
===Possible mentor(s)
@MRaishWMF ; Design Research manager Gabriel Escalante
===More details
====AIMS & GOAL
Better understand those who use translation and edit across multiple language versions of Wikipedia. Understand their motivations, goals, and challenges in a way that informs product development to support their efforts.
====IMPACT
We expect this project to have direct implications for product teams (including but not limited to the Language and Growth Teams), helping them to better understand the experience of multilingual editors as well as identify product interventions to support their work.
====OUTPUTS
Analysis and shareable report of the survey. We also welcome the opportunity to make space for direct sharing and discussion with relevant Wikimedia Foundation teams.
===Microtasks
Links to easy and self-contained tasks on Phabricator that students could work on to get familiar with the project. GSoC / Outreachy candidates are required to complete microtasks during the application period to prove their ability to work on a three month long project.
//These microtasks will require the applicant to pay attention to examples of surveys they encounter in the course of their normal online activities, and to pick one or more of them to think about in detail.//
* Survey thinking: find an example of a survey you’ve recently come across (any topic):
** What kinds of information is this survey trying to access? Try to identify as many specific kinds of information as possible.
* Survey thinking: Choose one or two questions that you think work really well
** Why do they work well?
** What kind of information are these questions trying to access?
** Can you think of different ways to ask these questions? How does changing the wording change the way the questions work?
* Survey thinking: Choose one or two questions that you think don’t work well
** What kind of information is the question trying to access?
** Why isn’t it as effective as it could be?
** Try to come up with a few alternative ways this question could be phrased. How does changing the wording change the way the questions work?
Please share the results of these microtasks here in this ticket in the form of a Google doc.
==October 4 update==
Thank you all for the amazing interest in this project! As stated above, please simply leave a link to your microtask submissions in the form of a response to this task. You can add me via email (mraish@wikimedia.org) as a viewer/editor/commenter to your document if you'd like to keep the document itself private. Thank you again, and stay tuned for more communication!