If you are accepted, fields that are marked "(public)" will be displayed on a public acceptances page. If you prefer different information to be displayed publicly than you want to provide in this form, please provide both a private version visible only to the coordinators and mentors of Outreachy, and a public version to be displayed publicly.
Do you meet the eligibility requirements outlined at https://wiki.gnome.org/Outreachy#Eligibility (if no, explain why not)?
Preferred pronoun (e.g. she, he, they):
IRC nick (public):
Internet presence (e.g. web page, blog, portfolio, GitHub, Twitter, LinkedIn links) (blog will be displayed publicly):
Location (city, state/province, and country) (public):
City: New Delhi
Education completed or in progress (include university, major/concentration, degree level, and graduation year):
University: Netaji Subhas Institute Of Technology, New Delhi
Education in progress: Junior Undergraduate
Major: Computer Engineering
Degree Level: B.E
Graduation Year: 2018
How did you hear about this program?
A friend of mine participated in outreachy (Round 13). Also many senior students of my university have performed well in GSOC.
Are you applying for Google Summer of Code and, if so, with what organization(s)?
Yes, i am applying for Google Summer of Code with Wikimedia organization for single image batch upload project.
Please describe your experience with the organization's product as a user and as a contributor (include the information, as well as a link or an attachment, for the required contribution you made to the project you are interested in here):
As a user, idea of the project seems fascinating as it will ease out the work required to upload images at Wikimedia:Commons by users from GLAMs.
There will be plethora of advantages as-
- No manual uploading is required- easy upload on one button press.
- Flexibility to upload multiple images at same time.
- No requirement of any technical knowledge.
- No need to deal with permissions.
- Everything will be automated from tag fetching to title generation, no need to enter any details.
- Overcoming the hassle(download, metadata updation, etc) required to upload an image from an external source.
As a contributor i find this project challenging and exciting, both at the same time. I find it challenging as it will extract the best out of me and exciting because it will allow me to work on something new along under some talented mentors. This project doesn’t have an already existing codebase which will allow me to explore for options and select the best out of the lot which implies no limitations. I love automated things as they ease out one’s work and this project will allow me to contribute to such an automation. As a contributor the problems which this project will resolve will majorly be batch uploading, no uploading of duplicate images with different names on Commons, no need to design different upload scripts for different GLAMs and making the process of uploading modular.
Please describe your experience with any other FOSS projects as a user and as a contributor:
I have contributed to FirstAide-Web app by systers organization which is a very handy tool for people in emergency situations.
Please describe any relevant projects that you have worked on previously and what knowledge you gained from working on them (include links):
Online-Treasure-Hunt: I have developed a platform for online treasure hunt. This is a ready to use portal to host an online-Treasure-Hunt. I built it for a competition hosted by the technical society of my university. It is coded in native PHP and is safe from various security flaws. From this project i have learnt how to deal with the problems encountered in a live running code. From this project i have also gained knowledge of various aspects of security issues and improved my coding practice to make my code efficient and flexible.
Survive: Web portal for a Disaster Management Android Application android application. It is designed for volunteers where they can register and receive messages. I have also deigned API through which information can be exchanged between web portal and android application. It is build in PHP. It is a project of my first hackathon, through this project i learnt how to make a final product in a simulated time and realized the importance of modular and efficient coding.
Face-Recognition Tool: This is a simple python script which detects faces in an image. This project was a good learning experience for me. I majorly learnt about OpenCV and python through this project.
Hospital-Hacks: It is an interface made to reduce the gap between hospitals and the patients. It aims at automating all the thought process that goes into looking for a hospital around one’s house considering their needs. It gives access to live scenario of the hospital to the user. Doctor and reception interface is built in PHP and for user there is an android application.
Moksha-Website: This is a portal for Inter college festival of my university. I have coded a few APIs for event registration and contestant registration for this website. Through this project i learnt to code modularly and gained an experience to work with with a huge team.
Content-Management-System: I have also designed and coded a content-management system for computer society of my university. It is developed to smoothen the content control of website and social media platforms. This project helped to learn how to integrate various APIs into my code efficiently. Through this i learnt to deal with all the permissions issues required to access external sources.
What project(s) are you interested in (these can be in the same or different organizations)?
I am interested in Single Image Batch Upload project which is under Wikimedia organization.
Please describe the details and the timeline of the work you plan to accomplish on the project you are most interested in (discuss these first with the mentor of the project):
The main objective of this project is to ease out the workflow required to upload images released by GLAMs(acronym for Galleries, Libraries, Archives, and Museums) to Wikimedia: Commons. It also aims at overcoming the problem of batch upload due to which multiple irrelevant images gets uploaded, as user does not intend to do manual uploading of each image. This project aims at building a Flask platform from where users can upload a single or a small set of images at the same time to Wikimedia: Commons through a well structured process and in minimum possible time. This project will also deliver a robust set of APIs to support integration on GLAM’s end.
- Precise Flask design for backend and frontend of the framework.
- Setting up frontend for the platform.
- Coding of upload script which includes the following:-
- Getting GLAM's API access
- License verification of uploaded files
- OAuth permissions for authentication of users
- Fetching image from URL
- Building final upload template from metadata mappings
- Setting up a structure on Wikimedia: commons which will include the following:
- Making a landing page for the product
- Adding categories for GLAMs
- Designing of metadata-mappings for GLAM’s APIs.
- Working on date parsing, feedback, file title generator and a few more default functionalities.
- Connecting with communities to pitch them for our product.
- Technical User documentation and documentation for users.
- Deployment of framework on Toollabs.
Proposed Flow Of Framework
May 4, 2017 – May 30, 2017
This phase will include community bonding along with investigation and design planning of the tool.
- Study the requirements of the project to more depth to have a more clear scenario and discuss them with mentors.
- Study already existing tools for uploading images to Wikimedia: Commons which will allow to compare different techniques and methods to achieve the same goal.
- Getting Toollabs access and trying it a bit to understand its working properly which will help in deployment.
- Learning more about metadata fields and various techniques to fetch them.
- More Investigation on the needs of GLAM users to design our tool accordingly.
- Compiling list of GLAMs.
- Preparing Phabricator tasks and categorizing the project into multiple phases.
- Design proper workflow along with finalizing precise design for frontend and backend.
Minimum Viable Product(MVP)
The minimum viable product aims at completing the following tasks before the end of June:-
- Designing a simple UI for the platform.
- Tool to generate template for upload file using metadata mapping of selected GLAM.
- Coding an upload script in a proper working condition which will be able to upload files to Wikimedia: Commons using OAuth permissions along with license verification of uploaded files
Week 1 (June 1 – June 7)
In the initial week, i will be focusing on the working of the following functionalities:-
- Setup a quick and simple UI
- Identify selected GLAM from the hash table
- Call to GLAM’s API and getting API access key
Week 2 (June 8 - June 14)
This week will include dealing with following aspects:-
- Selection of image(s)
- Dealing with Licenses
- Writing user and technical documentation and testing of the code.
Week 3 (June 15 – June 21)
This week will focus on the following:-
- Getting URL of image
- Download image and check if it already exists
- Collecting tags and generating filename for the image.
- Build final template for upload file using metadata mappings
Week 4(June 22 -June 28) - Week 5(June 29 -July 4)
This would be the final phase of coding upload script.
- Upload file using OAuth permissions.
- Testing and documenting of upload script.
- Deployment of MVP on Toollabs
- Writing user documentation and testing the MVP.
By the end of June, Minimum Viable Product is completed and is tested.
Week 6(July 5 -July 11) - Week 7(July 12 -July 18)
From July onwards i will start working on Core extensions
- Setting up a structure on wikimedia: commons, creating some categories and sending proposals to a few communities.
- Designing a few mappings along with default functionalities such as date-parsing, title generator, connecting to wikidata elements, etc.
- Testing those mappings with upload script
Week 8(July 19 -July 25)
- Connecting with communities who seems interested.
- Working on feedback to add something more to default functionalities.
Week 9(July 26 -Aug 1) - Week 10(Aug 2- Aug 8)
- Designing a few more mappings along with default functionalities.
- Testing those mappings with our upload script.
- Working on improving the front end.
Week 11(Aug 9 -Aug 15)
- Completing user and technical documentation.
Week 12(Aug 16 -Aug 22) - Week 13(Aug 23- Aug 30)
- This phase will involve rigorous testing and making the required changes. And fix subsequent bugs encountered.
- At the end of the internship program the Final report is submitted for evaluation.
|Tasks to be completed||Timeline|
|Community Bonding Period, get better understanding of the project, exploring existing tools, get familiarized with Toollabs and get its access , prepare workflow and precise design layout for frontend and backend.||04/05/17-30/05/17|
|Setting up a simple UI along with Coding upload script in a proper workable condition||01/06/17-25/06/17|
|Testing MVP and deployment of MVP on Toollabs (Phase 1 evaluation)||26/06/17-04/07/17|
|Setting up structure on Commons, Designing metadata mappings along with default functionalities.||05/07/17-18/07/17|
|Connecting with communities and working on feedback||19/07/17-23/07/17|
|Designing a few more mappings and improve the front end. (Phase 2 evaluation)||24/07/17-08/08/17|
|Completing user documentation||09/08/17-15/08/17|
|Testing and updating Deployment||16/08/17-22/08/17|
|Freeze code and final Report Submission .(Final evaluation)||23/08/17-30/08/17|
Micro-Tasks Carried Out :
- T161328: Designing of templates and mockups for the proposed flow of backend and frontend. Github Link: https://github.com/kamsuri/Single-Image-Batch-Upload
- Upload on commons: Uploaded images to Wikimedia: Commons using Upload Wizard of Commons and Pywikibot to get an idea of OAuth Authentication, Copyrights and License Verification.
- T161945: Designed scripts for date-parsing according to the format compatible with Wikimedia: Commons. Github Link: https://github.com/kamsuri/date-parsing
As MediaWiki uses Phabricator which is a set of powerful tools used for managing bugs and tasks, I also intend to use it for tracking bugs, features. It is also helpful for getting feedback from people who are a part of the organisation.All bugs and features will have tasks linking to the project, which will allow easy tracking and monitoring.
The code base will also use Git for reviewing and managing workflow.I'm comfortable with using Git for project development and management.
I can be contacted on email or IRC, also I intend on using my new blog for sharing my experience while working on the project.I will try to weekly update my blog by writing new posts.
I believe IRC and Mailing lists are great place to seek help.It would also be great to get in touch directly with my mentors via email if possible.
If i get selected, GSOC will be my main area of focus during summers.
- I'm 19 year old Junior undergraduate of Netaji Subhas Institute Of Technology pursuing Bachelor of Engineering in Computer Sciences.
- I enjoy working on open source technologies and love to contribute.
- I like to work with new technologies and explore new areas. I have a good experience of working in teams.
- It is always a learning experience to understand practical development at large scale. I also enjoy working on competitive programming problems and learning algorithms.
- Works as Director Of Web Operations at CSI NSIT.
- Worked as Front end designer at Ecounsellors.in for duration of 6 months.
- Academic Courses : Object oriented programming, Algorithm Design, Operating systems, Web technologies
-Frameworks and Libraries: jQuery, Bootstrap
-Operating Systems: Linux, Windows
-Tools: Git, Adobe Photoshop
-Database : MySql
Will you have any other time commitments, such as school work, exams, research, another job, planned vacation, etc., between May 30, 2017 and August 30, 2017? Please provide exact dates for these commitments and the number of hours a week these commitments take.
I have my college vacations from May 30 to July 25. Although i am enrolled in a college internship programme which is mandatory for all the students from May 29 to July 21 but GSOC will be my main area of focus if i get selected. I will be available for minimum of 5 hours(7:00 pm to 00:00 am [Indian standard time]) on weekdays. On weekends the schedule would be to work on a minimum of 8 hours(11:00 am to 07:00 pm [Indian standard time]). I will be working on this project for minimum of 40 hours a week as per my above schedule. My internship programme and classes will take maximum of 23 hours a week.
If a student, please list the courses you will be taking between May 30, 2017 and August 30, 2017, how many credits you will be taking, and how many credits a full-time student normally takes at your school. Please provide a link or upload your program's suggested curriculum by semester, which includes the suggested number of credits in each semester. Please provide a link or upload your school's academic calendar.
A full time student normally takes 27credits for a semester, but if a student is enrolled in a programme the project credits
are not required which are about 12(3credits*4projects) credits for a semester.
Academic Calendar: https://drive.google.com/open?id=0B0KJtMR93IZaZjhpeG1Ic1hNaXc