This is my first post for Hactoberfest. Just because this is the first contribution to the real open source project contribution was more than enough to make me interested.
This first issue was suggested by the professor, in the beginning of this course, I asked him about how to choose a good open source project fit to me and he suggested to me this repository called "Kubernetes". And because it is a big open source project, there were lots of big and small issues that needs to fix. Among the lots of issues, the one that attracts me was Korean localization issues, there were lots of missing and wrong Korean translations and It was stated in one of the issues that they need a Korean native speaker to work on it. But there was a lack of a translator who knows the coding. Hence, I decided to work on one of those Korean localization issues.
The issue I chose, needs to change the mistranslation in the files on the Kubernetes Korean translated site. To be specific, it was a misunderstanding of Korean. This is because, in Korean, even though it is English if it is a term, then we just write in original English words by Korean, but if we run that in google translator, it translates it into full Korean but it even translates the terms which can make confusing to the user. This is because it does not have enough understanding of the Korean language with culture.
In this case, the main part of this issue was mistranslated of PodCondition and NodeCondition as those terms which should be written how it spells in English. I researched the Kubernetes blog posts written by Koreans and they are just using the English term instead of translating it into full Korean which can make users more confused.
The setup part took much longer and needed more research than I expected. I thought I can just run by using npm right after I download the app. However, I needed to download ruby and GNU to Run the application in my local to check the changes I made were applied well.
The files that I need to edit were MD files. I edited 3 different files and it took more than I expected. This is because the pages were about the details of the application using the Kubernetes, I needed to read a lot of the web pages to understand the context and change which only needed to fix.
Just an example of what I fixed is
- I changed "조건" to "컨디션" to make the sentence more understandable.
While I am working on this issue, I faced 3 difficulties. First is as I mentioned I need to understand the application, so I need to research a lot learn about it.
The next difficult part was to sign on CLA agreement. After I push the code to the branch, I created pull request, However, it kept failing on pull requests and it said that I did not sign on CLA, even I already signed it. I joined Kubernetes open-source slack to ask what happened and I even contact the CLA agreement customer service. However, the reply from customer service was so slow and the people in the slack channel does not have an idea about what happened to me. So, I need to research on google and I found a way that I can check the git id and see if it matches.
Unfortunately, my id for git bash was wrong. So, I changed the git bash id to match my GitHub ID. After I change the id, the pull request was successful.
I think the most interesting conversation was the CLA agreement. Because I had conversations in both slack and on the pull request. and I did not know that my git bash id does not match with my GitHub ID, because there was no problem before.
Top comments (0)