Skip to main content

Fixing Bugs Again

I started working on Open Source Projects again and I had a difficult time getting started again. A big part of my problem was not having enough storage on my computer. After moving some things around and deleting files and programs I don't use, I was able to clone a couple projects and I was finally ready to start running them and replicating the issues. 

This time around, I worked on three projects; Thimble, Brackets, and Balrog. The bugs that I fixed for Thimble turned out to be fixes on Brackets so the pull requests were made there but referenced from Thimble. Overall, getting started was much easier than last time because I already had the experience and possibly the necessary files on my system to begin.

After being assigned a couple bugs, I began to work on them and I have made a couple pull request for the fixes. They have passed all tests and I am just waiting on it to be accepted and merged into the actual project! That is my goal. I will need to follow up if anything goes wrong and I will update my blog with more updates. 

Everyone I've worked with so far is very helpful and nice and welcoming. Balrog had a nice IRC where I joined and was immediately greeted by a couple people. A lot of the conversations I had was there and they directed me and helped me fix the bug. This time around I tried to not ask but when I got stuck, I did end up asking for help. Very helpful people and I really enjoy conversing with the Balrog team.

For Thimble, my teacher was one of the hotshots in the project so he was the one directing me and helping me along the way. For the most part, I was able to figure out what was wrong and fix it. All my pull requests passed the automated tests and they are waiting on being reviewed. It seems like the project owners are on Christmas break or vacation or something so it doesn't look like I'll be getting merged anytime soon. The project did look inactive at the time but who knows, I will definitely have an update when things change.

This time around, I was already familiar with Github because I've had a lot of experience in the past couple months. I had no problems with forking, cloning, committing, and merging.

I had a fun time working on bugs and I'm going to try to work on some more before the new year to gain even more experience. I  am also looking forward to taking the next Open Source Development class next year at my school so I can continue to learn and contribute to Open Source.

Comments

Post a Comment

Popular posts from this blog

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 t
Post a Comment
Read more

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
Post a Comment
Read more

My Journey of Fixing Bugs

Fixing bugs in the open source world is completely new to me. It's something I've never done before and it is something that I am really looking forward to. Being able to say that I've contributed to so and so sounds very fulfilling. I am ready to start working on bugs. To start off, I picked three bugs and I left a comment asking to be assigned if no one else is assigned. So now I have to play the waiting game. I will be doing research on the bugs so I can be prepared for when/if I do get it assigned. I chose two bugs from Thimble and one bug from Firefox(Android OS). The android one seems simple, and can be found  here . I'm not really interested in this one but I'm using it as a backup to my backup. It seems to be just cleaning up and renaming. Which I think I can manage. The runner up to that bug is a bug from Thimble which can be found  here . This bug is a feature request that I think I am capable of fulfilling. It is to add line numbers to the console o
Post a Comment
Read more