=Profile=
**Name** : Keerthana S
**Email** : keerukeerthana8@gmail.com
**IRC nick** : keerthana
**Blog** : https://developerbytes.wordpress.com/
**Github** : https://github.com/keer25
**Location** : India (UTC +5:30)
**Typical working hours** : Between 2 pm and 3 am UTC +5:30
=Synopsis=
The Wiki Ed Dashboard / Programs & Events Dashboard is a Ruby on Rails + Javascript application that helps people organize groups of newcomers to contribute to Wikipedia. This project aims to use ORES (Objective Revision Evaluation Service) to provide specific useful editing suggestions to newcomers about how they can improve existing Wikipedia articles or article drafts they are working on. This can give an idea of what kind of improvements are needed for the article and gives them a jumpstart in their contributions
**Mentors** : @ragesoss, @Capt_Swing
=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 4 to May 30|**Community bonding period**. UI design for displaying the feedback messages with links to provide feedback on the suggestions. Designing UI mockups. Framing questions for the feedback form.|
|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). This enables only the respective editors to receive feedback for their Sandbox drafts. Adding a toggle/filter UI to switch to only My Contributions in the Activity tab and in each row of feedback button will be present. |
|June 13 to June 19|Design feedback form (link to which is present in modal opened by the feedback button) . UI for admin user to view the feedback responses collected. Announce feature in mailing lists or through other channels to the community|
|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 ORES.|
|June 26 to June 30|**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=
- Feedback buttons in articles/editors/activity section.
- Collecting and viewing feedback responses
- Improving the feedback messages with the help of the feedback responses with ORES features.
- Identify areas of improvement for ORES and make feature requests to the community.
**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=
Currently in the sophomore year of B.Tech in Engineering Physics in Indian Institute of Technology, Madras. Heard about this program in a campus wikimedia hack session. The odd semester starts on August second week but I will be able to commit enough time for the project as there are no exams during the period.
I am eligible for both Outreachy and GSoC. I am applying for both the programs with the same project. I am hoping that this will be a kickstart into open source development. This would be a great way to get exposure on real world applications, collaboration of code and interacting with the open source community.
What inspired me to work on this project is that I like the concept of letting students submit assignments as wikipedia content which the whole world can see and review rather than as a term paper to the professor. I would like to continue contributing to this(Wiki edu dashboard) project and it would be great to see it implemented in more universities worldwide.
=Past Experience=
I have gained experience with Ruby on Rails and VCS (specifically git) by working in college techops teams to design portals for several organizations in college.
I like to participate in Appathons (I develop Android apps) and have creates several Android apps.
I have developed a game Quantum Chess (hosted at http://qchess.bitballoon.com/ ) with Unity3D (UnityScript).
**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