===Profile Information
Name: Yael Luria
Web Portfolio: https://yaeluria.github.io/
LinkedIn: https://www.linkedin.com/in/yaeluria/
GitHub: https://github.com/yaeluria
Location: Israel
Time Zone: UTC+3
Typical working hours:
Sun, Mon, Tue, Thu: 9:00 -14:00 and 16:00 - 19:00,
Wed: 10:00 - 14:00, Fri 9:00 - 13:00
(flexible)
===Synopsis
WikiContrib is a tool for community members to visualize their technical contributions within a specified time range. Currently, the tool gathers statistics from Phabricator and Gerrit.
This proposed project will be to work on current bugs and further enhancements to this project. Features proposed for this projects are:
- 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.
- Fetch the best user avatar and about information from the possible venues and display it alongside the contribution statistics.
**Mentor**
@srishakatux
**Have you contacted your mentors already?**
Yes, I’ve been contributing to the project since the beginning of March.
===Deliverables
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.
**April 27th - May 19th (before the internship starts):**
Preparation for the internship - improve my knowledge of Python and the Django framework.
Look over the project and the bugs/issues mentioned in the repository. Ask the mentors any questions and document any bugs/ issues I come across.
**May 19th (internship starts) - June 1st:**
Research existing bugs
Defer any bugs that should be fixed after implementation of the new features and fix the ones that should be fixed before starting to work on the new features.
**June 2nd- 30th : Work on the feature to count contributions that are 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.).**
**June 2nd - June 9th:**
Plan visualization for displaying the data on github contributions. Make mockups. Build a basic ui and test with dummy data.
**June 9th - June 16th:**
Work on the Backend API to fetch the data on github contributions.
**June 17th - June 23rd:**
Continue Working on the Backend API to fetch data on github contributions
**June 24th - June 30th:**
Improve the UI for displaying github contributions. Add any necessary front end code e.g. to parse the fetched data. Test and fix bugs.
**July 1st - July 28th: Work on the feature to count technical contributions made by a user on-wiki**
**July 1st - June 7th:**
Plan visualization for displaying the data on on-wiki contributions. Make mockups. Build a basic ui and test with dummy data.
**July 8th - July 14th:**
Work on the Backend API to fetch the data on on-wiki contributions.
**July 15th - July 21st:**
Continue Working on the Backend API to fetch data on on-wiki contributions
**July 22nd - July 28th:**
Improve the UI for displaying on-wiki contributions. Add any necessary front end code e.g. to parse the fetched data. Test and fix bugs.
**July 29th - August 4th:**
Work on the feature to Fetch the best user avatar and about information from the possible venues and display it alongside the contribution statistics.
**Aug 5th - August 11:**
Test the app. Fix deferred bugs. Improve implementation of the features if necessary.
**Aug 12th - August 19th:**
Wrap up the work and add documentation for the new features. Document any bugs if these still exist and could not be solved during the scope of the internship. Write issues for new features/ enhancements.
**do you see any risks/concerns involved with implementing the planned features?**
Since there will be a lot more data visualized once we get the contributions from Github and on-wiki, I am concerned this about keeping the visualization clean and organized. I think I will have to put some time into planning every feature as well as how the app would look with all the features combined. Another concern is the pre-existing bugs that I am concerned will take some time to solve and might not leave less time to work on the planned features. I therefore allocated a considerable period in my internship schedule to work on the bugs, and also prioritize which ones should be dealt with at the beginning, and what should be deferred to the end of the internship.
===Participation
Describe how you plan to communicate progress and ask for help, where you plan to publish your source code, etc
I will continue to push changes from my local fork to Github, open pull requests, comment on issues and pull requests. I will document new issues on Github, and also use Phabricator, if advisable.
I will communicate with my mentor on chat if I need assistance and meet her for weekly video chat meetings.
===About Me
Tell us about a few:
**Your education (completed or in progress)**
I am a self taught developer specializing in Web development, with good knowledge of the JavaScript and the React framework. My knowledge of programming comes from watching online tutorials, reading documentation and mostly from building my own Projects.
**How did you hear about this program?**
From a friend.
**Will you have any other time commitments, such as school work, another job, planned vacation, etc, during the duration of the program?**
I will have no other time commitments but I plan to take the day off on May 29th and July 30th to observe Jewish Holidays.
**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)?**
I am only eligible for Outreachy, and only applying to the WikiContrib project. Another project I was applying to cancelled its participation in the internship program.
**What does making this project happen mean to you?**
It would mean a lot to work on this project since WikiMedia is a very important organization and I strongly identify with its mission to bring free educational content to the world and help fill the education gap. I personally use a number of WikiMedia tools on a daily basis and they have helped me with my education in several fields. I think it’s very important to have a centralized tool to track the activities of contributors and make it function in the best way possible.
===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**
I’ve started contributing to open source about 2 months ago (February 2020) as a collaborator on the Public Knowledge Workshop (https://www.hasadna.org.il/en/) Anyway Newsflash Infographics project, which aim is to provide reporters and the media with ready made widgets that display information and statistics on traffic accidents in order to create public awareness and pressure the decision makers into solving problems that lead to such accidents. Through working on this project I’ve learned a lot about git and github workflow, how to work in a team and best practices in software development.
You can view my approved pull requests for this project here:
https://github.com/hasadna/anyway-newsflash-infographics/pulls?q=is%3Apr+is%3Aclosed+author%3Ayaeluria+
These are my pull requests to the wikiContrib project during the outreachy application contribution phase:
https://github.com/wikimedia/WikiContrib/pull/141
https://github.com/wikimedia/WikiContrib/pull/132
I’ve also worked on a number of personal projects including a chrome extension that has about 25 weekly users: https://chrome.google.com/webstore/detail/focusalarm/ilcajdpmgfbeggnpffmohcopdgpcdndh