===Profile Information
**Name**: Shivani Gangadharan
**Resume**: https://drive.google.com/file/d/13YOl5ZXHqf9BO-i_TmmKsHBwQ4aqN1Cs/view?usp=sharing
**Location**: Delhi, India
**GitHub**: https://github.com/shivanigangadharan
**LinkedIn**: https://www.linkedin.com/in/shivani-gangadharan-bb893b15a/
**Timezone**: UTC + 5:30
**Typical working hours**: 10 am - 12 am UTC+5:30
===Synopsis
- Short summary describing your project and how it will benefit Wikimedia projects**Short summary describing the project and how it will benefit Wikimedia projects**
Wikicontrib is an essential tool that provides a good visualization of a user's contribution to Wikimedia projects made on Phabricator and Gerrit. This tool would be extremely handy for the Wikimedia community to evaluate people solely on the basis of their contributions and efforts, thus ensuring perfectly collated results. With a click, you get all the contributions of a user and using filters, you can also restrict to view contributions of a certain time period. When given a thought, this project actually has a lot of space for embedding new features and will grow to become one of the most frequently used tools.
Following are the features proposed for this project:-
- Counting technical contributions made to Github repositories under Wikimedia and other popular projects that are not necessarily under the Wikimedia account (e.g., WikiEduDashboard, apps-android-commons, etc.).
- Counting technical contributions made by a user on-wiki such as modules and templates, user scripts & Gadgets, etc.
- Possible Mentor(s) - Fetch the best user avatar and about information from the possible venues and display it alongside the contribution statistics.
- View total contributions of multiple users in a gallery form, for a particular Wikimedia project, that helps us decide who contributed most effectively in that project.
**Necessity**:
The features proposed above solves one of the major roadblocks of Wikicontrib ie., creating a larger and more accurate impact by fetching contributions made in Github as well. Since Github also very widely used, when evaluating candidates it would only be unfair if their GitHub contributions are not included for analysis. So once this essential feature is implemented, the project would already be halfway there or even more, on its journey to becoming a success.
**Mentor(s)**: @srishakatux , @Rammanojpotla , @Tuxology
- Have you contacted your mentors already? Yes
===Deliverables
| Period| Task
| ----- | -----
| Apr 27 - May 14| **Community bonding**, fixing more issues, thoroughly exploring backend part of the codebase and becoming familiar with the tech stack used.
| May 15 - May 19| Build designs of the proposed features and a blueprint of their best possible implementation or workflow, and also making required changes suggested by mentors.
|May 20 - May 28| Work on highest priority feature of including Github contributions of Wikimedia
|May 29 - June 1|** Initial feedback** and improve the code structure and documentation so far.
|June 2 - June 8| Work to include contributions on other popular repositories that are not under Wikimedia account
Describe the timeline of your work with deadlines and milestones, broken down week by week. Make sure to include time you are planning to allocate for investigation, coding, deploying, testing and documentation|June 9 - June 11| Ensuring the two features added so far are in sync and do not have conflicts or disturb the overall functioning and look of the tool
|June 12 - June 14| Building workflow for fetching best user avatar and about information from the possible venues and display it alongside the contribution statistics.
|June 15 - June 22| Work on fetching best user avatar feature and its proper display
|June 23 - June 25| Working with mentor and ensuring best implementation of newly added features
|June 25 - June 27| Building UI and workflow steps for viewing total contributions of multiple users in a gallery form,
|June 28 - July 9| Implementing multiple user-contributions in gallery view by using best code practices
|July 10 - July 11| **Mid-point feedback** along with code cleansing, comments and updating the documentation
|July 12 - July 15| Wrapping up all new features included so far, fixing all issues and ensuring smooth functioning of the tool. Also, working with mentor on microtasks and any issues in wikicontrib project
|July 16 - July 18| Build workflow and UI design with mentor for adding a new feature that enables us to view the contributions of multiple users in a single Wikimedia project in gallery form such that it enable to analyse who made the most effective contribution in that project
|July 19 - July 30| Work on the above feature with best code practices and documentation update
|July 31 - Aug 1| **Feedback **from mentor and resolve any remaining issues or conflicts
|Aug 2 - Aug 4| Building UI and workflow for expanding the tool to gather specifically technical contributions in a particular domain or stack.
|Aug 5 - Aug 15| Working on the above feature and ensuring its smooth accommodation in the tool
|Aug 16 - Aug 18| Resolving any pending issues, conflicts and final updates to documentation
|Aug 19 - Aug 22| **Final feedback **from mentor and completing suggested tasks, if any.
===Participation
How I plan to communicate progress and ask for help, where I plan to publish my source code, etc:
- I will use my currently forked repository of Wikicontrib to make commits and send PRs to the synced original repository. This way, it will be smooth to work together as well as minimize conflicts in merging PRs.
- For effective communication with mentors, I will communicate on IRC and Zulip in my working hours and in non-working hours I’d be available on Gmail.
- Issues or bugs related communication will be through comments on the Github issue or PR.
- Lastly, I’ll keep adding weekly targets achieved on my meta wiki [[ https://meta.wikimedia.org/wiki/User:Shivanigangadharan | page ]].
===About Me
- I am a 3rd year student pursuing Bachelors of Technology in Computer Science.
- In August 2019, I was asked to deliver a talk on open-source opportunities for women at the Sheroes office. So while preparing and researching for that talk, I got to know about Outreachy and ever since then I’ve been wanting to be a part of it. I applied because Outreachy highly encourages absolute beginners of open source to apply and learn from amazing people. And, an applicant is unbiasedly evaluated on the basis of their effort and willingness shown via contributions and communication.
- During the Outreachy internship program, I would have no other time commitments.
- My aim and focus is entirely on the Outreachy program with WikiMedia Foundation. I strongly believe that this will help me to become very comfortable with open source and from the experience learnt, next time I can mentor other aspirants with their open-source journey.
- From the very moment I made my first little contribution to this project, it has and will continue to hold a huge significance for me. I want to make this project stand out, make a solid impact and I consider it my responsibility to make that happen. I have been constantly motivated by WMF and their vision. This project, WikiContrib, is an essential and handy tool that will save us a lot of time when observing a person's overall contributions on Wiki and GithHub. Plus, it is absolutely perfect for a dedicated beginner like me and has a lot of scope for expansion.
===Past Experience
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). If you have already written a feature or bugfix for a Wikimedia technology such as MediaWiki, link to it here; we will give strong preference to candidates who have done so
===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