Release 0.2 - PR 2

 Hey PC readers,

Welcome back to my blog!

This week we had to complete PR 2 of the Release 0.2 along with the Lab 4. I did Lab 4 yesterday, hopefully you read my blog about that too. Anyway, I did PR 1 with one of the repository that I stumbled upon while looking for a good first issue for my Release0.2 on a total stranger's repository from anywhere around the world. I was trying to understand his usage and installation instructions while I realized the readme's grammar was a mess and sentences were killing me. I could not understand properly, so I fixed that in my PR1. Going with the flow of DPS 909, everything has to be bigger than the last, you can say complex too. So of course no more, small grammar issues for sure.

I started looking for the good issues, with hacktoberfest or docs label maybe. Lots and lots of searches went throughout the week. I could not finalize one repository to be honest. I felt like this is too complex for PR2 or too simple for PR2. I came across a repo which uses Rust and I know nothing about Rust. I thought maybe let's give it a try. I starting going through their issues. One of the issues was to add a License badge to their readMe file. I thought that I did add License once for my repo but don't know much about it. So I started researching more about the licenses, badges, license and copyright information with readme and GitHub repositories etc. It was something new and I thought would make a good work experience for PR2. The problem was that this issue was already assigned to someone else but that person never worked on it or if they did, they never got back to the owner/moderator. I already researched a lot on various types of licenses and stuff, so I thought to ask the moderator to let me work on this one. Better make a PR or contribution to the unknown repository to remember I did something, I know the knowledge will always stay. But eh, PR is a very greedy business. LOL.

I forked their repository and created a branch with the same issue name and edited the Readme to add the License badge. The project used the Apache 2.0 version licensing and needed to have a badge with that only. They already had multiple badges in their readme , I added the asked license badge by editing their readme. I committed these changes and created a Pull request for the same and tagged the issue with that one. It might not be a very big one but it was certainly a informational PR for me. I never knew how to add badges too, but now I do along with the licensing information.

My issue: https://github.com/interledger-rs/interledger-rs/issues/158

My PR link : https://github.com/interledger-rs/interledger-rs/pull/655 

 

Well, this was a fun PR, as usual so many new things to learn in each week in this course. I am glad I took this course to be honest. It is a load of work for sure, but worth it.  See you in my next blog!

Best,

PC