|**Timeline** |Task|Remarks | Work report | Status|
|Week 1 (Due May 18)|Community Bonding period||[[https://developerbytes.wordpress.com/2017/05/08/gsoc-2017/ |First Blog post]]|Done|
|Week 2 (Due May 25)|Community Bonding period|Introduced myself to the community through mailing list. Joined Zulip. Discussed with mentors about participation during GSoC. Learning new technologies for the project.|[[https://developerbytes.wordpress.com/2017/05/18/community-bonding-period-week-2-of-gsoc/ |Week 2 - Blog Post]]|Done|
|Week 3 (Due June 1)|Community Bonding period|Updated deliverables. Did some research on the dashboard and finalized the goals of the project. |[[https://developerbytes.wordpress.com/2017/05/26/community-bonding-period-week-3-of-gsoc/ |Week 3 - Blog post]]|Done|
|Week 3 (Due June 1)|Design and add buttons in the MyArticles component that would display the feedback|The feedback buttons will be a way for users to say how each and every aspect of the suggestion was useful and would be designed in a more sophisticated manner in the future.|[[https://developerbytes.wordpress.com/2017/06/03/week-4-the-coding-period-begins/| Blog post]]|Done|
|Week 4 (Due June 8)|Add feedback based on ORES features|The features are retrieved and processed in the rails backend to generate feedback. They are not stored in the backend as of now. They are retrieved in the frontend through Redux. The features based feedback should be improved.|[[https://developerbytes.wordpress.com/2017/06/13/rendering-the-rails-controller-json-output-with-redux/ |Blog post]]|Done|