GSOC 2015/Student Application rahulrrixe

Project Title : Fresque

Contact Information

Name: Rahul Ranjan E-mail: rahul.rrixe@gmail.com IRC nick: rahulrrixe at irc.freenode.net Phone: 91-9819737113 Fedora Profile: Rahul Ranjan GitHub: rahulrrixe Blog url: https://medium.com/@RahulRRixe Website: http://rrahul.me Location: Allahabad, India, UTC +5:30

About Me

I’m a Senior student at Indian Institute of Information Technology, Allahabad majoring in Information Technology. I have excellent proficiency in Golang, Python and C/C++. I am passionate about building real time scalable web application. Furthermore, in past I have gained experienced in all the major web frameworks i.e. Flask, Django, ROR, and Martini. Apart from this, I am also comfortable with front-end technologies i.e. Javascript, CSS and HTML. My Open Source journey started when I became Mozilla Student Ambassador and initially my contributions were limited to localization and community building. Later on it expanded to code contribution. Recently, I was contributing to release engineering groups projects. Links to some of my contributions are mozregression and releng API. Why do you want to work with the Fedora Project? I have been using Fedora for past five years and I am fond of its user friendly interface and reliable support forum's. In past, I have contributed to fedora-infra tahrir project and I must say that I had "great learning experience" while interacting with my mentor. I like fedora community and find everyone very helpful and motivating. In last few years, I have found some great projects has been started in fedora-infra like ptogit, shumgrepper, fresque etc, to which I would like to contribute. Do you have any past involvement with the Fedora project or another open source project as a contributor? Yes, I have contributed to fedora-infra tahrir project. I have made contributions to several other open source organizations i.e. Apache, Mozilla. Apart from these I have also made contribution to python projects on github i.e. Python-Cliff and Python-Click. Why should we choose you over other applicants? I have 3+ years experience in Python language which is basic required skill of the project. Fresque project is a flask app and I know the framework very well. Apart from these, I have experience in writing unit tests, handling database and also coming up new ideas. This project will involve development in flask, sqlalchemy, pygit2, unittests etc, which I know pretty well. I have already gone through the fresque project workflow and made few contribution to the project and thus, I think it makes me a strong candidate for this project. Did you participate with the past GSoC programs, if so which years, which organizations? Yes, Last year I have participated for the Apache. The project was about developing command line application for Libcloud API. The project repository is available on on my github page. Will you continue contributing/ supporting the Fedora project after the GSoC 2015 program, if yes, which team(s), you are interested with? I would love to work more with Fedora-Infra team because their projects intersect with my interests. I was working on Progit, Tahrir for some times and after GSOC, I would like to contribute to these projects as well as fresque. Will you have any other time commitments, such as school work, another job, planned vacation, etc., during the duration of the program? In early May our summer vacation of college will start and ends by late of July; I can give my full time commitment to this project,. I assure dedication of at least 40 hours per week to the work and that I do not have any other obligations from early May till mid August.

Past Experience

In past I have made contribution to various projects of Mozilla and Apache foundation. Recently . Moving ahead, I have also written two open source libraries i.e. Parinx: Sphinx docstring parser language which provides a interface to extract the relavant parameter. Sec-Edgar:Download all companies periodic reports, filings and forms from EDGAR database, which are available on pypi. Apart from this I have cofounded "Prequell" whose first project was scaling Flask application using blueprints and celery. Finally, I consider myself as an experienced Python developer as I have built various application across different domain using it. Prior to GSOC, I have completed internship at The Walt Disney Company and their I have worked on building highly personalized real-time news application using Golang and Python.

Goal

Fedora Fresque is a standard Python web application that abstracts away intricacies in package review process. Currently for any package to enter the fedora repository has to go through the manual review process, during this period they receive valuable feedbacks but once the package gets imported; all the information is lost. So, I will develop a web application which will expose dedicated RPM reviews using inline comments along with some level of automation. This will bring up lot of new possibilities to package manages and will allow them to connect to the packaging reality.

Project Details

The project will consist of 4 main phases:

Phase 1: Add git server on backend

The current process of package review have no git integration and with every new build of the package we looses the information of previous one. It means we are depriving the evolution of the spec file. Adding git will help us to track all the changes. The process workflow can be described as When ever a new request for package review will be requested, a bare git repository with same name as of the package gets created on the fedora review server. The bare repository keeps tracks of the changes made by the packagers. Now packager can clone this git repository on their local machines and can make changes to it. Thereafter they can push the updated code to the fedora review server git repository. The changes data will be saved in the review server repository. For example: Rahul submitted spiderman package for review and update his package with .spec file. The process using git will look like below. $ git clone git@fedorareviewserver.org:/var/git/rahul/spiderman.git $ cd spiderman && touch spiderman.spec $ git add spiderman.spec $ git commit -m "initial commit" $ git push -u origin master Branch For every target release their will be separate branch in order to avoid the conflicts during revive process. To keep it more general, the branch name will be given as fNN such as f14 for Fedora 14. This will be set to the default master branch.

Phase 2: Streamlining review process

No inline comments. Currently the feedback is done by creating Bugzilla ticket. Ask Questions and get answers — right in the code Ask questions about the code you use, and get answers from our community of experts, using full Markdown with syntax highlighting and symbol linking.

Phase 3: Fedora-Review integration

No automatic QE during review. Fedora-Review implements API which removes many manual process in review process by doing automatic checks. People use own spreadsheet and other tools to keep track of changes. unclear for what you are waiting for. People forget about fedora flags. Bugzilla don't know about fedora relationship. like who is packager and who is the reviewer. Review Server: Git enabled server which also contains lookaside cache and tools and automation tools. every push will upload new tarball

Phase 4: user friendly GUI and robust unit tests

Deriverables

Web front-end and backend of fresque Deployment of the app Documentation and Manual Unit Tests Integrating of the app with other applications

Timeline

Period Task April 27 - May 14 Community bonding, reading documentation and getting familiar with all the codes. May 15 - May 24 Writing unit tests for the previous already written functions and fixing bugs. May 25 Official GSoC coding period begins. May 25 - June 09 (2 weeks) Git Backend Phase - Development of fedora review git server. June 10 - June 17 (1 week) Add HTML file browser for git repository. June 18 - June 25 (1 week) Review Process Phase - Adding backend functions for review process. June 25 - July 03 Mid term evaluation period. July 04 - July 14 (10 days) Front-end interface development for the review process. July 15 - July 31 (2 weeks) Fedora-Review integration Phase: add fedora-review tool for automatic testing of new reviews Aug 01 - Aug 05 (5 days) Web-Front end development which involve creating user friendly design and embedding security features. Aug 05 - Aug 12 (1 week) Writing unit tests August 13 - August 20 (1 week) Sanitizing codes, documenting everything, reviewing all the functionalities and fixing bugs. August 21- August 27 (1 week) Pencils down period. Submitting the project for final evaluation. References Getting new package into Fedora for first time contributors Review Server: Package Reviews without Bugzilla" by Pierre-Yves Chibon & S. Ochotnicky Pygit2 Documentation Fedora-review, help yourself! Package Review Process