Rahulrrixe (talk | contribs) No edit summary |
Rahulrrixe (talk | contribs) No edit summary |
||
| Line 98: | Line 98: | ||
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. | 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. | Adding git will help us to track all the changes. | ||
The process workflow can be described as: | ;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. | * 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. | |||
For example: Rahul submitted spiderman package for review. The process using git will look like below. | |||
<pre> | <pre> | ||
$ git clone git@fedorareviewserver.org:/var/git/rahul/spiderman.git | $ git clone git@fedorareviewserver.org:/var/git/rahul/spiderman.git | ||
| Line 107: | Line 111: | ||
$ git push -u origin master | $ git push -u origin master | ||
</pre> | </pre> | ||
|- style="background-color: #e6e6e6;" | |- style="background-color: #e6e6e6;" | ||
Revision as of 19:55, 24 March 2015
Project Title : Fresque
|
Contact Information |
|
|
About Me |
I have been using Fedora for past five years and I fond of its user friendly interface and reliable support forums. In past, I have contributed to fedora-infra tahrir project and I must say that I had "awesome experience". I also enjoy fedora community a lot, find everyone helping and always encouraging. Till now, I have contributed to only one project and I am looking forward to contribute to more projects.
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 contributed to several popular python projects on github i.e. Python-Cliff and Python-Click.
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 and also maintaing big projects. This project will involve developing web-frontend using flask, 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.
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.
I would love to work more with Fedora-Infra team because projects are really cool and they completely intersect my line of interest. I was working on Progit for some times and after GSOC, I would like to contribute to this project.
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.
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.
For example: Rahul submitted spiderman package for review. 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
|
|
Phase 2: Streamlining review process |
|
No inline comments. Currently the feedback is done by creating Bugzilla ticket.
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 |
|
|
Timeline | |||||||||||||||||||||||||||||||
|
