Skip to main content

My first bug fix: Completed

Fixing bugs is a lot of work. Fixing bugs for an open source project is even more hard work. If you have no idea what you are doing, it is very difficult to contribute. Fortunately, the open source world welcomes new people. My experience with working in open source was difficult but so satisfying.

I ran into a few bumps before I could actually start working. I talk about those bumps in my previous blog posts. I realized that I had no idea where to start. I had never worked with a project this big and I was intimidated. I did not know where to start.

I was having a very hard time, my head was hurting, I was feeling dumb, and I was beginning to give up. But then help came to help me. One of the guys over at Mozilla was a big help. He took his time to email me personally to check up on me. I was shocked that he did that.

I replied and we started chatting on IRC. He wanted to help me and he was very knowledgable. He suggested another bug for me to work on to get more familiar with the python language. He said that I can keep the bug that I was assigned and I can try to work on it again when I'm more comfortable. I accepted the new bug from him and I started working on it immediately. The bug can be found here.

It seemed to be a more simple bug that required me to remove code that is no longer being used. I found this job to be very easy and I did it really fast. I was excited and I asked him where I can submit my code. He said wait, slow down, have you tested the code? I responded yes, it runs exactly the same way. He said you need to run the built in tests using a certain command "./run-tests.sh" I was like oh, okay. I did it and I was waiting and waiting and waiting. It ran and ran and finally, I couldn't believe my eyes, it said no errors found. I was very excited at this point.

I rushed back onto IRC and said the tests were successful and he told me to commit it to my cloned version of Balrog and then to do a pull request so he can review the code. He reviewed it and told me to fix one more thing and then commit the changes again.

I changed what he asked, but this time, the automatic tests that are on github did not pass. He told me that it's a formatting issue. There should be 2 lines of spaces between classes instead of one. I changed it, and the tests on github passed.

Finally, after waiting and waiting, my code was accepted and my code was committed to the official Balrog project. I became a contributor to Mozilla and I felt so accomplished over a small little bug. Overall, it was a long difficult journey, but the satisfaction of seeing the end result is very motivating. I look forward to working on more bugs in the future both in this course and even after my school career.

It was a fun experience and I want to be able to contribute to many other open source projects that I am interested in.

Comments

Popular posts from this blog

My Journey of Fixing Bugs...Again

Last week, I left comments asking to be assigned to bugs in Thimble. I was excited to get started but I was informed that the bugs were already taken. And the worst part is that the person who was assigned is a fellow class member. I didn't know if I should be disappointed or happy for him. Anyways, as soon as I found out that none of my bugs were going to be assigned to me, I started commenting on other projects like Balrog, and I managed to land three bugs! Two in Balrog and one in network-pulse-api. I want to work on Balrog first. At first I was having a lot of trouble trying to build the Balrog project. I was running into errors and I kept figuring out how to fix them and I just couldn't get passed one. I was searching for days, i was just staring and not getting anywhere at one point. Finally, I decided to ask my teacher for help and he simply said, talk on IRC. I was a little skeptical but I did what he said and I was greeted and helped within minutes. The guy helpi