=Profile=
**Name** : Anne
**Email** : annemachinda@gmail.com
**Github** : https://github.com/Lukong123
**Location** : Cameroon (UTC +1)
**Typical working hours** : Between 8 am and 4 pm UTC +1
=Synopsis=
The Multilingual Wikipedia Editor Survey internship project aims to gain a comprehensive understanding of individuals who contribute to Wikipedia by editing and using translation across multiple language versions.
The goal of this project is to get a better understanding of those who use translation and editing across multiple language versions of Wikipedia. Understanding their motivations, goals, and challenges in a way that informs product development to support their efforts.
**Mentor** :
=Final Summary=
- After the project, an Automatic feedback feature is successfully included in the Wiki-Ed dashboard that is shown in the MyArticles component that shows the articles edited by a particular user and also shows them in the Articles Edited Section for the suggestion to be reviewed by instructors.
- There is a feature for users to add their own suggestions on the edits in addition to the Automatic Feedback.
- Adding an easy way for users to give feedback on this feature.
- Even if the Automatic Suggestions couldn’t be made smarter as part of my project I hope the work done to document the ORES features would encourage such improvements.
- Making a spreadsheet of the ORES suggestions pointed to some blatant errors in ORES predictions due to redirects and the issue is notified in this [[ https://phabricator.wikimedia.org/T170434 | task ]].
=Next Steps=
- I couldn’t contribute to making the Automatic Suggestions smarter as I lacked some experience with Wikipedia Editing and this is a major scope of improvement for the project.
- Adding the feature for custom user suggestions on the edits in the Article-Viewer component where it could be more relevant.
=Timeline=
| **Period** | **Task** |
|------------ |-----------|
|May|December 4 to May 30December 15|**Community bonding period**. UI design for displayUnderstanding the feedback messages with links to provide feedbackvarious groups we will be working on the suggestions. Designing UI mockupsand any new tool. Framing questions for the feedback form.|Come up with at lease first full survey questions |
|May 30 to June 12|Creating buttons for pulling feedback in articles section under all subcategories (example : Available articles) and for pulling feedback in every row of contributions under an editor in editors tab (but only visible on logged in editors' contributions).December 18 to December 29|Analysing, This enables only the respective editors to receive feedback for their Sandbox drafts.onses, Adding a toggle/filter UI to switch to only My Contributions in the Activity tab and in each row of feedback button will be presentdoing research where needed and providing a detailed report for the work done during the first month. |
|June 13|January 2 to June 19|Design feedback form (link to which is present in modal opened byanuary 12|Learnig from the feedback from the feedback button) irst months. UI for admin user to viewStudies and research for the feedback responses collected.next survey questions, Announce feature in mailing lists or through other channels to the community|releasing the questions.|
|June 20 to June 26|Improve the feedback with ORES features with the help of feedback received and find other features that can be helpful in giving feedback to find areas of improvements in ORESanuary 15 to January 26 26||Analysing, responses, doing research where needed and providing a detailed report for the work done during the second month.|
|June 26|January 29 to June 30February 9|**Phase I evaluation**|
|June 30 to July 7|Design Onboarding UX for users to get introduced to the feature which can improve feedback. |
|July 8 to July 14|Write feedback based on the article grades(ORES predicted) using https://en.wikipedia.org/wiki/Template:Grading_scheme .|
|July 15 to July 31|Designing method to measure how the feedback affects the following edit and collecting data(Needs more investigation) and improvements in feedback messages based on the feedback responses received.|
|July 28|**Phase II evaluation**|
|August 1 to August 8| Improve feedback based on the data collected on the effectiveness of the feedback messages. |
|August 9 to August 15|Improvements based on the feedback responses received and find and document useful features that can be added to ORES.|
|August 16 to August 28|Bug fixes, Writing documentation and Updating appropriate guides. Code cleanup for submission.|
|August 29 to September 5 |Mentors submit final student evaluations|
|September 6|**Final results of Google Summer of Code 2017 announced**|
|--------------|-------------------|
=Deliverables=
- Comprehensive analysis of survey responses: The end product of the project will involve conducting a thorough analysis of the survey data collected from multilingual Wikipedia editors. This analysis will include examining and interpreting the responses to gain insights into the motivations, goals, and challenges faced by these editors.
- Research report: A detailed research report will be compiled, summarizing the findings from the survey analysis. The report will provide an overview of the key findings, trends, and themes derived from the data.
- Insights for product development: The research findings will help identify areas where product interventions can be implemented to support the work of multilingual editors.
**Phase I evaluation**
- Onboarding UX for the automatic feedback feature.
- Feedback based on article grades (ORES predicted).
- Data based on the feedback of the previous version and the subsequent edit.( To identify target users, articles &c.)
- Improving the feedback messages with the help of the feedback respones with ORES features.
- (Optional) Including in the feedback messages how the edit has improved from the previously given feedback
**Phase II evaluation**
- Improve feedback based on the data collected on the effectiveness of the feedback messages.
- Document useful features that can be added to ORES.
- (Optional) UI of thumbs up/down to mark the feedback helpful.
- Write documentation and update guides.
**Final evaluation**
=Participation=
- Work on a separate branch on git and uploading code to the forked repo almost on a daily basis. Creating pull requests as and when a complete feature is done.
- Online on IRC in my working hours ( 2pm to 3 am UTC +5:30)
- Communication on tasks will be through commenting on subtasks to the project created on Phabricator.
- Weekly reports will be published in my meta wiki [[ https://meta.wikimedia.org/wiki/User:KeerthanaS | user page ]]
- Publishing on my blog the summary of a task at the end of a task period as above in the timeline( https://developerbytes.wordpress.com/)
=About me=
I am currently a Masters Student at the University of Bamenda in the field of Computer Engineering. I am tech motivated and an open source lover. I am opened to the field of Software and Data Engineering.
The aspect of analysing data is a motivating part of this project for me. Moreover the fact that this analysed data will be used to help product development to better the experiences of the numerous multilingual editor is also a very encouraging factor for me, because this will go a long way to help the population.
=Past Experience=
I have acquired experience collaborating within teams like GDSC(Google Developer Student Club) co-lead and co team member, Technovation Girls Mentor etc.
Being in school, I have being opportuned to have and validate courses on Data Analysis, Data Analysis and Mining, Machine Learning which provided me with relevant knowledge understand and analyse data.
I have examined community surveys to support the project demonstration for both international competition and personal project.
**Microtasks completed**
- Processing slow process async by implementing sidekiq workers
- https://github.com/WikiEducationFoundation/WikiEduDashboard/pull/1223
- https://github.com/WikiEducationFoundation/WikiEduDashboard/pull/1227
- https://github.com/WikiEducationFoundation/WikiEduDashboard/pull/1228
- https://github.com/WikiEducationFoundation/WikiEduDashboard/pull/1229
- https://github.com/WikiEducationFoundation/WikiEduDashboard/pull/1230
- https://github.com/WikiEducationFoundation/WikiEduDashboard/pull/1245