Stella's Blog

  Release 0.2.4 Now I am at almost the end of release 0.2 and I chose the telescope as the final contribution. To be honest, this is huge, well organized and great project and it is first time to take a look. Unlike my previous assignment during the previous terms, there are tons of what I have never seen. First, docker compose is great and the document for contribution is very clear. Of course, I had no idea when read it first, but every time as my professor mentioned, there was a great guy, helper?, helping me a lot to set up the project. Although I had no idea about Elastic-search and Redis-cache server, I was happy to take a time to look though the codes and to understand. Again, trying to understand an issue is always hard for me and sometimes I am really not happy when somebody does not understand my question. This happened again. The reason why I attached the picture is that I am still confused about the whole process of this project especially about why frontend didn't get ...

  Starting... This lab is to practice about the advanced skills on git such as rebase, squashing, and amend. What I had done before I learned this way to handle my incorrect committed message was like that, just doing reset and doing it again. I can say that I really love this skill especially about rebase and interactive amend mode. Progressing... Actually, This task is very simple and I understand the main purpose is not refactoring my code, but using the advanced git skills for my future journal in the code world. With the instruction of osd600, I made 3 commit messages to try to rebase for squashing three messages. pick   b77bdc5  applied three refactoring like used function, getting rid of global variables and removing duplicated regex and rename the methods squash   28059dd  got rid of global variables squash   66e551b  removed dupli...

  Starting... This lab is to help students to communicate with the owner in open source world to solve the conflicts of merging their branch to remote origin. So, following the instruction, I forked one repository that I chose and create an issue to add new feature of ignoring url patterns from a file. git clone https://github.com/StellaJung-Student/project-checkurl.git Progressing... Actually, The main of my task is not about the implementation above. It is just helping another classmate to help his or her task complete. Of course I also have had the part from another student so I added his repository as another remote one. My issue on my repository is issue-11 so I typed following command. git checkout -b issue-11 pedro/issue-11 He did great for the task but I realized that he didn't modify readme for the feature of ignoring urls so I created issue-11-fix. git pull pedro issue-11 git checkout -b issue-11-fix pedro/issue-11 Git is actually so great since it automatically prov...

  Release 0.2.2 ~ 3... Now I am in the middle of release 0.2 and it is very exciting and I am pretty sure I am enjoying it now. Today, I have learned how to set up the husky which is about when I try to commit codes, it automatically checks if there is an issue or unmatched rules to standard based on eslint and prettier. Firstly, I added comment to get the responsibility of the eslint and prettier set up issue. After I added the comment, I tried to get some advice to complete this issue and he made a comment about his favorite way of setting up husky. Here is the  link  which is very helpful since there are very specific format to set up and actually, it was almost the same except the main language.  During the following the process, I realized another issue that he also created is very related my current issue so I also added a comment to take the issue and he gave a kind of agreement emoticon. This was the eslint that I created after understanding of eslint. Pretti...

  Starting... This lab is to help students to solve the conflicts of merging their branch to master. So, following the instruction, I created two issues which are about  Create a filter for status code  and  Use color flag to use color output . Both of issues came from same commit position from master. Progressing... The first step I took is I added the new feature and commit and merge to master branch. From this OSD600 course, I have learned new library, Yargs, from the lecture video, and a lot of classmates already used it. Hm, I am a slow-starter LOL. Anyway, after applying the library and little bit of code change, I merged to master branch and there was no problems. By the way, following my professor's instruction, I tried to use  providing code to blogger, gist  to avoid using just image. And this is my first merge result. Next, I moved the issue-8, which is about color option from Node environment. To make the test easier, I used dotenv library. How...

Release 0.2.1... To be honest, this, looking for a task in the open source about Hacktoberfest, is very very competitive and it turns out so stressful.... Is it only for me? First day of October, I tried to research bug by the way that I learned from OSD600 course, with below command. As you can see, it seems very popular. More than 14,000 issues are wait for you~ but actually there are so many developers working on the open source world, which means that by 30minutes issues come out, most of them make comments. Although, you have been commented by the first, it doesn't mean you will take the job. PR is actually a real competition.  Language also very important. Javascript is the most popular language in this Hacktoberfest and Python follows as the second one. As my professor mentions that the first issue doesn't need to be difficult or code issue since there is a lot document or css issues but it is actually more competitive. To avoid this terrible competition, I tried to comm...

  Starting... Today, I have learned how I can search to access and take a task from open source world. I have appreciated to github to provide a lot of opportunities. I was very busy today to create Twitter and following my professor, hacktoberfest  and so on. First experience is not really good. What I learned from the first stop to contribution is actually kind of a competition. Even thought I made a comment, somebody just came up and with a short comment and it is just closed with PR from the person. It is very different from this open source course's previous labs.  Therefore, I should try to find out a new issue that I can contribute.

  Starting... I have been very exciting to review other classmates' repository before I will jump into a real open source project. From this lab, I have learned how to do forking and cloning other projects and create a new branch for a new issue or a new feature. It is very hard to wait for the owner's answer but it also can be a special experience  Reading... In my experience, finding an issue and improvement is not easy especially for other's task and really careful to touch it since it should be very sensitive. For this reason, my first step for this lab, I tried to create an issue with a nice comment. During the time for waiting for reply, I did forking and cloning the repository and started to review a code to find out what I can contribute. Finally, I figured out some part I can improve so I added comment for it,  Issue 5 I suggested three things. First of all, the number of counter is always the last number so I wanted to fix it. Second, I wanted to add an another ...