Release 0.2 - Week #3

Hactoberfest 2019- Week #3

For the 3rd week of Hactoberfest 2019, I had to do some learning to finish the request which was excellent because I took on a request / issue that I did not know how to do myself.

For the issue, click here. 
For the pull request, click here.

First, for this issue/request required me to format the users read me file. His read me file consisted of a lot of permissions / commands that were listed with bullet points and it was structured in an unorganized fashion. For example: 

The way I contributed to his read me file was by cleaning it to look more aesthetically pleasing and I created data tables for his Features, Permissions, and Commands. For example: 

As mentioned before, this required me to do a bit of research / learning because I was unfamiliar on how to created tables/fix the code on the GitHub read me file. 

I felt like this request was a good experience for me because it gave me a chance to learn how to organize documentation on GitHub because that would be a required skill to have if I ever decided to create or put up my own code on GitHub. 

Release 0.2 - Week #2

Hactoberfest 2019- Week #2

For the 2nd week of Hactoberfest 2019, I worked on a bit more complex open source request / project than I did last week. It required much more time but I feel like I made quick a bit of progress on the issue.

For the issue, click here
For the pull request, click here

First, this issue/request required us to contribute to his code as much as possible. He had Several code files which were different Sorting Algorithms in different programming languages which included: JavaScript, C / C++ Programming, and Java. Pretty much it looked like an unsorted file of sorting algorithms:



The way I contributed to his code included:

1. Sorting his algorithms in sub - folders and based on the Sorting Type, I grouped them together. Like this:



Structure Change:
       Sorting(Folder)
                 BubbleSort(SubFolder)
                           - Files related to BubbleSort
                 BucketSort(SubFolder)
                           - Files related to BucketSort
                  ..... continuation

2. I did code clean up + documentation on functions / important parts of the code that required the user to understand what was happening.

This issue was a good experience for me because it required me to look at the code and make changes where I see fit. Except requesting specific changes, he let us take control and told us to contribute to his project as much as possible. Due to this, I was able to examine the code and find fixes on my own which is a good skill to have in general. The pull request has not been accepted yet, however, I hope my changes are up to his standard and they do get accepted.

Release 0.2 - Week #1

Hactoberfest 2019- Week #1

For the 1st week of Hactoberfest 2019, I worked on my first open source request / project. It was quite a simple one but I was glad that my fix was merged and accepted. 

For the issue, click here
For the pull request, click here

First, the issue for this request was that the user wanted a structural change for his web application. his index.html contained his HTML code, CSS code, and JS code, all in one. He wanted to separate this coding structure to look more like this: 

-docs/
   |-src/
   |-css/
      |-style.css
   |-js/
      |-dark-mode.js

Restructure the cod. Move style/css code to css folder and html to be in index.html file and js code to js folder. 

Thus, the css and javascript are in external files and are called from index.html. So, the changes I made included: 

1. Taking the CSS out of the index.html and creating an external CSS file called style.css in a folder called css. 
2. Calling the css external file from index.html
3. Doing the same as Number 1 with Javascript -- Except calling it dark-mode.js under the JS file. Called the js file from index.html as well. 
4. Cleaned the code a bit. 
5. These changes were made by forking the persons repo, then cloning the repo, made the required changes and I created a branch called "Fixes - #19". 

This was a great learning experience for me because I was able to understand and finish someones request in a good amount of time. I actually asked on the issue if I could work on this issue, however, before I could get a response, I could see that people were committing the code, thus, I quickly finished the request and made a pull request. Luckily for me, the other people who worked on it forgot some of the requirements and my pull request got merged instead of theirs.

 

Lab #3 - Octoberfest Preparation

Hactoberfest 2019 Preparation 

This is the first time I will be participating in the Hacktoberfest. It was mentioned in our Open-Source development class several times when we started, however, I didn't realize it was mandatory to do for the course and thus, I didn't have much interest in it until now. Due to the fact that it's required for the course, I am actually looking into it more and I realized that this is such a good opportunity and I should have take initiative and looked at this beforehand. For starters, I love competition and competing with other people to win prizes and this is a perfect example of that. The first 50,000 that complete 4 pull request(s) win t-shirts which I high-key want the t-shirt. 

 For this month, my goals include: 

1. get involved in a project that you find interesting

2. Work on code including HTML / CSS / JS; web - application development based.

3.  I want to work more with Git and Github Desktop 

 After researching some open issues available on Github, I found these three that look particularly interesting: 

1. Split html file into three different file and folder, restructure webpage #19 

2. Create a nice homepage #7 

3. Improve the UI #15 

I choose these 3 thinks because they have to do with HTML changes / additions / fixes.  To achieve these goals, I will look at the requirements and see if I am able to complete it. I will measure the progress based on the size of the issues and I will put the issue in my phone to keep track on how long I've been working on the issue.