Abdul's OSD600 Open Source Journey

My Issue/Addition       As I was searching for a new project/repo to contribute too, I just couldnt get over the feeling that my last PR was not complete to my satisfaction and I needed to make some changes to it before I could feel like I was done with it. I decided to create another issue on the repo to address these improvements Creating the Script/Making a Pull Request     I started out by researching the most popular online pc games and finding the servers that are used for most major regions. In my initial script, I was thinking on a more personal level and included only games that I play and that would really limit the usefulness of the script. Once I found as many games as I could, I added their information to the json file I had created to hold the game server information. I then had to modify the script code to accommodate these new games. Afterwards I updated the readme documentation to include the new functionality and made my pull request .  Review Process      The review

 Introduction     The idea of working on and contributing to an open source was something that caused me a lot of anxiety, seeing how large and in depth most of the repos I was looking at made me feel like I would be of little help or have very little to offer. As this stress kept building I defaulted to procrastinating and avoiding having to find a repo to contribute to. Finally, I decided that I would just need to jump in and begin to build my confidence if I wanted any hope of becoming a better programmer or succeeding in this class. I thought for my first pull request it would be easier to work in a language I was already working on for my release 0.1 and ended up finding a repo that was centered around curating python scripts. So I thought I would try contributing my own script to this repo.  My Issue/Addition          I was playing an online game one night ( league of legends) and I had got into a game and noticed that my latency was very erratic and needless to say that ruined m

 Lab 4 - Adding Feautures and Working on Separate Git Branches This week I worked adding and updating features to my CLI url status checker, DeadOrNot . I choose to update my link filtering flags to have my clear option names as all as add a flag for displaying all link information.  Setting up Separate Branches  I started out my creating two issues on github repo detailing the changes I was about to make. Then I made branches to match each of those issues. This has actually helped to maintain an orderly work flow as opposed to the more disorganized style of coding I fall into sometimes while working on projects. Having the issues separated in separate branches made it easier to stay focused on a singular task as opposed to trying to work on multiple things at once which is something I tend to do.  Merging the Branches to Master Branch  I thought the process of combining my changes to the master branch would be more difficult but the process was relatively simple and that is encouragin

Week 3 OSD600 - Pull Requests   This week, our class took a look at each other's release from the previous week and were tasked with finding an issue or suggesting an improvement/adding a feature and then implementing that fix or improvement in the from of a  pull request. This week I decided to once again took a look at Matt's CheckMyLinks python tool.  Finding Issues or Suggesting an Improvement While reviewing Matt's code, I couldn't really find any issues that I could fix, so I instead I decided to look for ways I could think of to improve his tool. I had a couple ideas but the one I decided to go with was to add an option that would allow the user to save the results of the link check to a text file. I thought this would be useful so the user can have a reference of the results after leaving the command line. I left an issue request on Matt's repo and began to implement the improvement.  Implementing Improvement   The first thing I did when starting to code t