Release 0.3: Internal Project (Telescope)

-

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 internal project. The website and GitHub link for the Telescope are the following:


When I looked around Telescope GitHub issues, I felt it is hard to find the issue I can work on. As it is the biggest project I've worked for this lecture and lots of students are already working on this project, it is hard to find a new issue for me. I kept reading the issues and finding the issues on the issue list and finally, I found one about UI! The title is 'Change Telescope Theme to a light theme'.

I left a comment whether I can work on this task and got a response. I started work on it for the 404 page or My Feed page.


When I run the project locally and see the 404 page and My Feed page, I felt confused. It seems that the pages were already changed to a light theme. When I tried to change the background colour to make it a more light theme, it changes other pages as well. I did not know whether that is what project members want or not. I just created a pull request about that and asked them whether it is okay or not. I started communicating with the person who already started the issue. He or she said they do not want to change the background colour but 404 page's button font colour to dark grey. Following his mention, I've changed the font colour and they approved my pull request! Now I am one of the contributors to the Telescope project!


While I am working on this project, I've learned the power of communication. I felt it would be better if I asked him/her saying the pages seem the theme is already changed to a light theme so please tell me if you want to change another colour. That might reduce the time for this task. I remember this lesson and will apply this in the future!

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