Release 4.0 - Part 2: Progress

-

For release 4.0, I need to work on a more difficult task than other issues I've worked on. The project I chose is Telescope which is the internal project of this course. The blog post for part 1: why I chose this project is the following: https://hyunjijanelee.blogspot.com/2020/11/release-40-part-1.html

As I have no idea about GatsbyJS and Next.js and don't know how the front-end works on the Telescope project, I've decided to spend my time this week researching and communicating.

Firstly, I communicated with the Telescope community. As I heard the task I take (error page) is partly done, I asked the person who took this before what parts are left so I will not mess up another person's work. He replied any of the front-end logic utilizes Gatsby aside from the router. I got I can fully work on this task.

Secondly, I read the documents about this task on Telescope GitHub. As many people partly take this issue (one person works on the login page, another person works on the footer component, etc), there are some documents to stark this task.

Also, I merged upstream master codes. As I forked Telescope repository a few weeks ago and the forked repository was beyond some commits, I added upstream remote and did merge it.

Finally, I researched how to port GatsbyJS code to Next.js. When I googled it, there are some documents on how to do it. Also, I've checked some pull requests already merged or created pull request related to issue #1316

I know the best way to learn code is diving into coding. I will spend my whole next week coding this task and completing. Actually, it is a little bit nervous to do a task using a language I am not familiar with. However, I believe I can do it with googling and community.

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

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.  Project name: Hasura GraphQL Engine GitHub link: https://github.com/hasura/graphql-engine 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 R
Read more