Hello Friends. Here I am going to explain what I delivered at MozTalk. I, along with Abhishek Potnis and Pratik Patil (who are my college-mates and project team members), successfully completed an open source project of Mozilla titled “An Open Web App for Editing Rich Text Documents”. For more details on concept of OWA, click here. You may also refer my slides which i presented at Talk.
Here I am going to explain right from how exactly we came across the topic to the completion of the project. The steps that we followed are:
1. Mozilla Student Projects: It was David Teller [:Yoric] who brought the project topic to our notice. He had created a list of student projects at github (Click here to see the list). When we had checked that time, there were only 7 issues in the list which today has increased to 55. We see that there are two tabs : Open and Closed issues. Open issues means that the projects are yet to be completed and Closed means they have been completed successfully. So we selected the issue #1 and commented on it to show our interest and also started working on it.
2. Github Repository : Github is one of the best methodologies of online collaboration. People residing at different geographical regions can collaborate easily on the same piece of code using github. Abhishek created a repository named editOnTheGo and we committed changes there. There are two approaches as concerned with repositories: fork an existing repository and work on it OR maintain a single repository and commit changes there. I was suggested the second approach to avoid merge-conflicts.
3. Hosting on github: As you can see on github repository, there are 2 branches: master and gh-pages. “master” is the default branch whereas “gh-pages” is used for hosting the page on github server. our project is hosted at abhishekvp.github.com/editOnTheGo/
3. Issues: A list of issues were created which symbolizes the tasks to be completed in the project. Here as well follows the same concept of Open and Closed issues. We self-assigned issues and started working on it.
4. Review by mentor: We used to notify the mentor on the completion on the issue. The mentor would review the code and ensure the working and well as check for any dead or redundant code. If there exists any, he would comment to bring it to our notice. Click here to view an instance of this.
5. Demonstrate on Firefox OS Simulator: OWA are primarily made to run on Firefox OS. Hence it is essential to test it on Simulator. It is available freely as an addon. Click here to add it to your firefox browser.
In this way, following the above steps, our project got completed in duration of around 6-8 months. There are few bugs and issues remaining but most of them are due to shortcomings of owa.Hope this information was helpful to you. In case of any discrepancies, feel free to comment here or contact me. My nickname is greatwarrior at IRC
Please make this post worth by extending your contribution to Mozilla bugs and student projects. Remember that even a small piece of code can bring a lot of change. We Mozillians encourage you all to participate to make the product even more better.
Note: Since I am a beginner, I may be wrong somewhere. So feel free to comment here and help rectify me.