Skip to main content

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 output. I am interested in this one because it is a project I've never used and it seems to be really useful for me in the future.

The one I'm most excited for though is found here. This one is also on Thimble. It is like a feature request/bug. Pretty much, I'd have to figure out how to change the description of a project without actually publishing it. Seems challenging but I'm ready for it.

I'm nervous because this is my first time and it seems very overwhelming, but I have the support from my teacher and I have all my classmates and the rest of the web that I can turn to. I'm hoping to learn how to work on bugs, learn things in a short amount of time, adjust and adapt to new environments and just things like that in general.

Open source is a huge part in today's tech society and I am really looking forward to be part of it and be involved in it. I hope I can make a lot of changes in the time to come.

Comments

Popular posts from this blog

Creating My First Repo

For my Open Source class at school, I had a lab to create a repo. This was my first repo ever and it was very fun to do. I had very detailed instructions on what to do and I got the hang of it very fast. It's interesting how open source works. I chose to use the Rust library to work on the lab. The lab is a multi step lab and will be added onto in the upcoming weeks. I had to design a library for obtaining file info. The best part about open source is that it is open source! Meaning as long as I follow the license rules of other projects, I can essentially reuse their code. Instead of reinventing the wheel, I can build on what already exists. And that's the power of open source. The next step for me is to use continuous integration in my project. I have never done this and it will be a good experience and it will be very valuable to learn because it is something that can be used in my future projects. I will talk about it more in my next blog.

Automated Testing

Automated testing is a very useful feature that is simple to implement in any open source project. It allows the testing to be automated to ensure that nothing will break when things are changed. In the open source world, code is changed quite often so having automated testing can make it easy to track and manage errors and we can know if the code is properly written to pass the tests. Overall, it is very beneficial in open source programming. Travis CI makes it very easy to link your Github page and the repos on it. It is very easy to get started and I would recommend it to everyone! I always used to do my testing by outputting the results and comparing it with whatever I had in my head, now, it does it all on it's own.

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...