Okay noted

Please I need clarifications on the proposal, I just made mine now and yet to see it amongst others. Do o have to wait for it to be uploaded there or I'm I making a mistake. Please I'm asking to be sure I'm not getting anything wrong

@awight, thanks for the feedback. Even If it's not a requirement in the program, I will make all adjustments needed as it would help me learn more and how to structure my works well

Please how do we get a review on of our timeline as the deadline is fast appreciate

Thanks for the feedback. I'll make some adjustments to that.

@Simulo thanks so much for the feedback. @awight and @Simulo how do we I get a review on my timeline

After so much struggling with finding my way around this particular task, I finally came up did something

@awight A review will be appreciated too

@Abhishek02bhardwaj Thanks for the concise feed back as I've been stuck for a while now

@Abhishek02bhardwaj please regarding the final application and Timeline, do we get an approval of our timeline from our mentors before submitting

@awight and @Simulo a review and feedback will really be appreciated as I had to make sure I participate in this particular task. This is a link to my repo

@awight please to be sure, does it mean this particular task is closed

This is an etherpad link to my contribution to my summary and Hypothesis. I will appreciate your review and feedback @Simulo @awight

Thanks @awight, I'll do that right away

Good day @Simulo and @awight can I make use of python to explore the data please??

Here is a link to my survey, I'm open to corrections. @Simulo and @awight I await a review and feedback

In T331207#8677994, @Simulo wrote:

Thank you for your answers, I will summarize my feedback here:

General concept: It helps to know what you want to find out and particularly, what your assumptions are. If you know your assumptions, you can put them to a test. We broadly wrote "The goal of the survey is to learn more about how this software is used" but that is pretty vague, maybe actually a question for a qualitative study. How do you think people translate? Can you learn something about translations from published research that informs your assumptions? With assumptions and questions about them you can focus your survey questions and the survey design.

Introduction: This is very important as it is what participants can use to see if they want to participate or not. Give the purpose of the survey but avoid merely repeating questions you are going to ask. Check if the language is clear. In this case, it might be tempting to use e.g. "qualitative" and "quantitative" here, but are reseracher jargon that might be unfamiliar to the participants.

Questions: Aim to make them both a) short and clear b) self-contained, so they can be understood without reading previous questions

Answers: As important as the questions you ask are the answers you allow…

Age: People might not like to give their age in years for various reasons, so age ranges are a good practice. The need to be unambigous: 20-30, 30-40 are ambigous – what do I check when I am 30? Better: 20-29, 30-39 or 21-30, 31-40

Gender: "How to Do Better with Gender on Surveys: A Guide for HCI Researchers" is my go-to resource (however, this does not mean that you need to take this route; some people might also opt for an open text field (in which case you need to think about how to analyse that) or not ask gender at all)

Nationality/Country: Important to keep in mind that the state controlling the territorry they are on might be different than the nation they see themselves belonging to.

Languages: Not easy, because it is unclear what skill level is meant. You could also set a definition like "good enough to write a Wikipedia article in that language" (which is not a perfect criterion, but at least something). If it is important to you, you could ask for their proficiency level. If that makes sense depends on your research interest (you can use more powerful analysis methods with rank-able items like a proficiency scale rather than a binary competent/not-competent scale, but it is more difficult to answer, so the question if it is worth it)

Reasons for translations, motivations etc.: To ask this you should have some good hypothesis of what you can to do with the data. As merely descriptive data of how participants are like they are not very informative (they depend on how people interpret them, how desireable the answers are etc.). They can be useful if you have an hypothesis like "people who are motivated by increasing coverage in their native language edit smaller wikipedias" (which would not be surprising, but can be tested)

Asking for frequencies: To better compare these, give some hints what you mean: "In the last month, how often did you…": Never/ 1-2 times/3-10 times/11-50 times/ more than 51 times (there are different scales you can use – look at some examples)

Means alot to me
Thanks @success

Means alot to me
Thanks @success

Means alot to me
Thanks @success

Hello everyone, my name is Precious. A newbie I'm the Data space and I would love to contribute my quota to this project. I am also opened/glad to be mentored by @awight