===Profile Information
**Name:** Nivas
**IRC nickname on libera.chat IRC (optional):** Nivas10798
**Web Profile**
**Resume (optional)**
**Location (country or state):** Andhra Pradesh, India
**Typical working hours (include your timezone):** 9 am to 12 pm and 5 pm to 12 am (UTC+05:30)
===Synopsis
//**Short summary describing your project and how it will benefit Wikimedia projects**//
**Project document:** https://phabricator.wikimedia.org/T304826
Campaigns are content/theme focused activities organized annually by collaborating with many volunteer communities and other government/private institutions. A hidden advantage of campaigns is, it acts as an open door to the Wikimedia world for new participants who are either interested or working in the field of the campaign theme thus improving the content and communities experiences. Therefore, a dashboard can give a better understanding of the retention of new users on various Wikimedia projects over different time periods after a campaign has ended.
**Possible Mentor(s):** **@Jayprakash12345**, **@Sadads**
- Have you contacted your mentors already?
-- Yes, contacted @Jayprakash12345
===Deliverables
Describe the timeline of your work with deadlines and milestones, broken down week by week. Make sure to include the time you are planning to allocate for investigation, coding, deploying, testing and documentation
===Timeline
| **Period** | **Task** |
|May 20 to June 12 | Community bonding period. Contributors to interact with project mentors and MediaWiki developers for guidance, discuss the outcomes related to the project and refine the project proposal (if needed). Learn Flask/Django and big data tools like Spark/Hive.
|June 13 to June 19 | Consult mentors, discuss building ETL pipelines and necessary data to create visualizations
|June 20 to June 26 | Build SQL query to extract necessary data from the databases for the selected campaign
|June 27 to July 10 | Check the dataset extracted from databases with project mentors. Start creating visualizations from the dataset. Finish visualizations and improve them by taking feedback from mentors
|July 11 to July 24 | Work on the building a prototype dashboard using web apps like Streamlit/Dash and present the prototype to the mentors
|July 25 to July 29 | **Phase 1 evaluation**
|July 25 to July 31| List out the necessary improvements for UI from mentors' feedback on the prototype and include them in the final dashboard created using HTML/CSS and Flask/Django
|August 1 to August 7 | Developing the frontend using HTML, CSS and backend using Flask/Django framework
|August 8 to August 14 | Integrate the backend with the frontend, check for bugs and fix them
|August 15 to August 21 | Display a demo to the mentors and take feedback for improvements
|August 22 to August 28 | Make improvements and test the final product
|August 29 to September 4 | Finish the final project documentation
|September 5 to September 11 | **Project submission and final evaluation**
|September 12 to September 19 | Mentors submit final evaluations of the contributor
|September 20 | **Announcement of GSoC 2022 results**
===Participation
Describe how you plan to communicate progress and ask for help, where you plan to publish your source code, etc
===About Me
Tell us about a few:
- Your education (completed or in progress)
- How did you hear about this program?
- Will you have any other time commitments, such as school work, another job, planned vacation, etc, during the duration of the program?
- We advise all candidates eligible for Google Summer of Code and Outreachy to apply for both programs. Are you planning to apply to both programs and, if so, with what organization(s)?
- What does making this project happen mean to you?
===Past Experience
- Please add links to any feature or bug fix you have written for a Wikimedia project during the application phase.
- Describe any relevant projects that you've worked on previously and what knowledge you gained from working on them.
- Describe any open source projects you have contributed to as a user and contributor (include links).
===Any Other Info
Add any other relevant information such as UI mockups, references to related projects, a link to your proof of concept code, etc