OSD600- Joey Assal

I really enjoyed this lab as is helped me understand the process/workflow of contributing to open source. I wrote a separate article on that which can be found here .  During this lab, I created an issue  on the original repository saying I wish to implement additional features to the code.  Once I got approval from the original author to do this I forked and cloned the project, created a new branch called issue-2 , and uploaded the code I wrote to it. After that, I made a pull request to the original repository. For my feature, I added the v and version arguments to their command-line tool. The process of getting my work accepted was exciting as I got to hear from the person who wrote the code and learn what it is exactly they want. This a great opportunity to improve on the code you wrote. One problem I had was after I got the feedback I was not sure how to edit code on the issue-2 branch, after doing some research I learned how to switch branches via the git checkout command. I al

The following are the steps/workflow you follow when you find a repository on GitHub and wish to contribute to it.      When you find an issue you wish to work on in a  repository , first fork it to your GitHub, then clone it and make a new branch (you will be working off this new branch. Its a good idea to name the branch after the issue you are planning to fix Eg. issue-2) . When you are done with your code push it to the new branch you made for the issue/feature then create a pull request ( pull request is a review request You are asking someone to check the changes on a branch before merging into another branch. ) The person who owns the code will check your code and if it's approved it will get merged with the original. 

  How did you go about finding someone to work with? I put up a message on Slack and got a reply from someone, I sent them my contact info and we revied each others code. What was it like testing and reviewing someone else's code? Did you run into any problems? Did anything surprise you? At first, it was a little  intimidating because I have never done something like this before, but after trying it, it was not as bad as I thought it would be. It's funny how a lot of times we are scared to do something but once we do it we realize we were scared for nothing. One minor problem I had was after I ran npm install to download the node modules I have to update some of them but after that, it worked great! There was nothing that surprised me. What was it like having someone test and review your code? Were you surprised by anything? Having someone review and test my code is a very good feeling because you know no matter what happens during the review, you will benefit from it. Two sets

What is release 1.0? For release 1.0 I created a command-line tool written in node to read a file given by the user, find all of the links in it, and test if they are working, broken or unknown. After it processes the file it outputs to the console all the links it found and the "status" of each one (working, not working, or unknown). When running the program the user must give one argument for the file name. If the user fails to do this the program will output a message telling the user they must enter a command-line argument which is the name of the file they want to process.   Features Features include: The ability to run the tool with v or version argument to get the version of the tool you are running. Colour coded output: green: working, red: not woking, grey: unknown Finds which links are broken, working, or unknow in a file Can process any file type (txt, html, ext...) Alerts user if they entered the wrong number of arguments Example usage Sample text file (test.txt):

Introduction: Hello, my name is Joey and I am a student at Seneca studying Computer Programming. My whole life I have always been interested in technology. Towards the end of high school, I enrolled in Computer Science and enjoyed the subject. My passion for technology and love of code persuaded me to get an education in Computer Programming. Why Are You Taking this Class? I am taking this class to help widen my skill set and also because I have always been interested in Open Source. I know many programming technologies such as Java, C++ and SQL but I don't know anything about Open Source. It has been a goal of mine to learn but never had the time to look into it. Therefore, I decided to take this class as I believe this is one of the best opportunities to learn!  What is it About Open Source that Attracted You? The freedom the comes with it. I am fascinated by the idea that anyone can take my code and work with it, and I can do the same to theirs. I believe the more people that co