Hactoberfest is very competitive

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 comment like that I would like to take this issue.. However, it actually make me more not confident. I really didn't have time to look at the project first, and just made the comment. After that, I realized the issue was too difficult for me so I said sorry~ I don't know what to say...

Finally, I found one that I could fix which is about adding LICENSE. I feel not happy to be honest since it was not an issue. However, it is true that I got the experience to make PR to a repository that I have never met. Hopefully, this experience helps other people who have not experienced about open source yet.

Comments

Getting more difficult?

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 ...

Working with telescope

Starting... This lab is to help students to communicate with a big project, telescope, and understanding how to handle with the set it up. There were a lot of trouble since many of technologies are new for me such as docker, docker-compose, elastic search ladis, pino, and so on. Let's jump in the big project . Progressing... The first step I took is to install wsl 2. It is not very difficult since microsoft provides good instruction, link . Although the telescope provides very good instruction, here , It was not really easy for me to get a concept and set it up successfully. Therefore, I needed to ask a lot of questions on slack, telescope channel. Some helped me a lot and explained so much and finally I got it work successfully. After my server was working locally, I didn't have any issue to get the response from the url, http://localhost:3000/posts. To communicate with the local server, actually I needed to change my code a lot since I wanted to sp...

Finally, release my first open source.

Starting... This lab is to release my product to install easily. Instead of cloning or downloading and setting it up manually, it provides a lot of convenience for users to install it. I chose NPM since I used nodejs. NPM is a great site to help develpers to release their git repository in the site. Progressing... First, I signed up on npmjs.com and logged in the site on the console to release my repository. I had to set up a lot of things like 'npm init', modifying readme and package.json to be ready. Second, I tried to release my repository by the command, 'npm publish --access public'. Unfortunately, the name, http-parser, was already taken, so I needed to change my name. I chose my name as http-checker and tried to release it again. At this time, I got 403, forbidden error. I spent a lot of time to figure out but it was actually due to not verified account. Once I got the verified email account, finally, I got the release version of my repository. Here is my...

Stella's Blog

Search This Blog