Release 0.3: External Project (Hasura GraphQL Engine)

-

For Release 3.0, I need to create two pull requests, one for internal Seneca College's project named Telescope and the other for an external project. This post is about the journey of the external project. 

After I've created a pull request for the internal project, I started finding an external project I can work on. There are thousands of issues on GitHub but I need to find a project which is bigger than I've worked for the release 0.2. To find a bigger project, I read the issues which have a number bigger than 100. I found some issues and asked whether I can work on it or not. Finally, I found a project I can work on named Hasura. 

When I looked around this project, I was surprised by how big this project and how many people contributed to this project. I would like to contribute to this project so started to read a README.md file and a contributing guide. When I scrolled down the README.md file, I found there is a README.md file translated with Korean which I am familiar with. I read the document and realized I can improve the wording on the Korean version of the README.md file. I've filed an issue for that.

After I've filed an issue, I started rewording the document. It took some time but I've done that. I created a pull request for this issue

It failed one check because it needs 'no-changelog-required' label which I cannot add to this pull request. I've added a comment asking to add the label to this.


I've learned my language skill also can be a huge asset to contribute to a project. It was really nice I can work on this project! Also, I've felt the power of communication while I'm searching for the issue for an external project. This issue is the one I've got the lesson: https://github.com/mojolicious/mojo/issues/1606

When I read this issue, I felt I can apply the knowledge I got from this week's lecture, adding a formatter. I asked the owner whether I can work on this task or not and started googling whether there is a formatter for the language this project use (thanks for that, I've learned there is a tool named 'Perltidy' which help to format the Perl source code!). After a few minutes, the member, author, and contributor started discussing whether they treat this as an issue they need to fix or not. That reminds me of the lesson I've got while I'm working on the internal project: the power of communication! It was a good lesson I've realized more about this while I'm a student.

Comments

Post a Comment

Popular posts from this blog

Lab 8: Automated Testing and Continuous Integration

-
When I developed a program, it was time-consuming to test all the functions I created when I add a feature. I needed to run each feature, check whether it gives expected output or not, and check all the output. It is possible I forgot to test a feature and later on, I realize I did not test the feature. I wonder if there any ways I can do it automatically. Now, I got the way how to do that. There is automated testing for it! To begin with it, I started searching the testing framework to apply my command-line tool named url-fi. There are some testing frameworks for Node.js such as Jest, Mocha, and AVA. The testing framework I chose is  Jest  which is a testing framework developed by Facebook. I've installed Jest running 'npm install --save-dev jest' and test whether it works properly or not.  This document  is the way I followed to install the Jest testing framework. After I've installed the Jest testing framework, I worked on separating functions. As my tool contains al
Read more

Open Source Project: Lab2 (Pull Request)

-
Image
 Introduction In this lab, I practiced contributing and submitting pull requests to other repositories I don't own. Following the lab instruction , the things I plan to practice are the following: forking and cloning other projects creating branches to work on new features and fix bugs working on code I didn't write, trying to maintain the original style and not break things creating pull requests collaborating with other developers on GitHub updating my pull requests to include fixes for review comments The Project I picked for pull request ( https://github.com/lixiaoqity/testLink/pull/7 ) I looked around the classmates' open source project and picked the project named testLink. The GitHub repository link is the following:  https://github.com/lixiaoqity/testLink/pull/7 .  I picked this project because it also uses the NodeJS which I picked for my project. It was really interesting to see how code can be written differently for the same subject. When I look over the project
Read more