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

Popular posts from this blog

Atom, My New Code Editor

Recently I started looking into a couple code editors for school. There were two that caught my attention; Atom and Visual Studio Code. After playing around with both of them, I decided to stick with one. Overall, they do similar things, but my decision is solely based on my bias. I personally am not a fan of Microsoft's software so I was not motivated to experiment with Visual Studio Code. Atom is a free to use code editor and can be downloaded at  https://atom.io /. The interface by default is dark, and it looks really nice in my opinion, but it can easily be changed by going into Settings>Themes It is really easy to customize it to how you want it to look. There are many things that can be changed, one controversial one being the spacing between tabs. It is really easy to get started with Atom. As soon as you start the program, you are greeted with a welcome page and we can easily start to edit anything we've been working on. The best part about Atom is that

Swift 4

There are a lot of languages out there to choose from when it comes to programming. Some are similar to each other and some are different from each other. Some are designed for a single purpose and some are designed for multiple purposes. A general programming language that was built to account for modern safety, performance, and software design patterns which is safe, fast, and expressive is a language called Swift. Swift is currently in it's fourth stage and the project became open source on Github in early December 2015. It is written with the languages; C++, Python, and Objective-C. It is associated with it's very well designed and detailed website called swift.org . Swift is used to create a good language for uses ranging from mobile to desktop to cloud services programming. For the most part, this language is being used by developers to develop applications for macOS, iOS, watchOS, and tvOS. Although it is open source, Apple has not allowed the Github community t

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