Name: Vinay Chandra Dommeti
Contact/Email/IRC nick:
IRC Nick: VinayChandra
Github: https://github.com/vinaychandra/
Background:
I am a Computer Science and Engineering Student currently in the final year pursuing my Bachelor of Technology from Indian Institute of Technology (IIT) Bombay. My B.Tech project includes work on python back-end (django) and HTML stack for the front-end.
My internship was completed successfully from Microsoft IDC, Hyderabad and I am offered a full time position in Redmond, WA. Several of my projects included web front-ends but unfortunately most of them are closed source from within IIT Bombay.
I am acquainted with AngularJS and it could turn out to be an important library for this project to create a Single Page Application.
Project title: Debsources on mobile
Project details: The aim of the project is to create a mobile friendly version of debsources, the source code navigation and interaction website for Debian. The current version is simply the desktop version and the same is displayed on mobile which makes it difficult to use. The goal is to provide a fix for this problem by making a responsive website.
Synopsis:
- The primary goal of the project is to create a Single Page application which would use ajax calls for retrieval of data from the debsources website. It would then be displayed on a mobile friendly responsive page which could be used for navigation of the source code. The second goal of the project is to provide an interface to edit the source code in mobile browsers so that it could be sent out as a patch to the concerned people.
Benefits to Debian
- The project brings mobile users the ease of viewing source right on their phones without zooming in and out for navigating along with editing of the source code without plugins on their browser.
Deliverables:
- A responsive single page application for mobile browsers with the ability to navigate the source code on their devices which use the already available apis' from debsources.
- Ability to edit and create patches from the application itself.
- Document and test the application thoroughly and update as deemed necessary by the mentors.
Project schedule:
My summer vacation starts on May 1st and I would be free up to the middle of September. So I would be working full time for GSoC. Before May 23rd, I have a few reservations, so I may not work full time although I keep in constant touch with the mentors.
I’ve tried to structure the timeline so that there are fewer weeks which are purely for coding or purely for learning. The last 1-2 days of a week will usually be reserved for code review and pull requesting (if necessary), though I intend to keep in touch with the mentor throughout the week and ensure that I’m going in the right directionBefore May 10th: Discuss the technology stack and the approach for the application with mentors and have a good idea on how a clear understanding on implementation details.
May 10-23: Setup the base project structure and the testing framework. The structure would be reviewed by the mentors so that we are in full sync before the takeoff of actual work.
May 23 - June 3: Implement the design and functioning of the mobile version of display of source code and listing of repositories in the website along with testing and documentation.
June 3- June 10: Iteration of changes after discussion with mentors. Also, start the work for the search functionality.
June 10 - June 17: Complete work on search including adavanced search.
June 17 - June 24: Pre mid-term evaluation. Any changes required would be made. The creation of remaining pages of the website would begin.
June 24 - July 5: The remaining pages of the website would be completed. The discussion on how to integrate code editing would ensue.
July 5 - July 15: A crude model of code editing would be done. This would include the basic functionality. This would require some experimentation with different libraries to find out which works best for the website. Feedback would be taken from mentors continuously to find the best method.
July 15 - July 22: Refined model for code editing and integrating completely with the website along with documentation and test cases.
July 22 - August 5: Iterations on improvements of design of the web page and testing on different browsers manually to find if there are any issues. Documentation of any undocumented parts and more tests if deemed necessary.
August 5 - August 20: Final evaluations and suggested pens downs date. Updates of any part of the website and internal testing within the group.
Exams and other commitments: The project would be as soon as my B.Tech ends. So, I am free and I have no other commitments until the final deadline of GSoC 2016 schedule.
Other summer plans: No other plans this summer. I have plans before the official start date (May 23) but none after that. My only work would be that of GSoC.
Why Debian?: Debian based operating systems (Ubuntu, etc) introduced me to a whole different area in computers and computer science including open source. I always wanted to contribute to open source and Debian is one of the most prominent members in it which impacted my life.
My previous Debian contributions: I have provided two patches for the debian project (#783911 and #782849) and one of them has been pushed and the other is under review. Although I completed another patch, I was informed that a patch already has been provided.
Are you applying for other projects in SoC?: No, Debian's project is the only one which I truly connected. This would be my only application for GSoC
