This week I got to Explore Seneca's Open source Projects. I worked On Telescope which shows the blogs of Seneca students. And I looked into the Seneca vs-code extension.
What I did for Telescope
My initial plan was to work on Issue 3639. It seemed to be a lot of work so I asked another developer Tong Liu for help where we would each work on a bit of the Issue. However, we soon realized that both of us couldn't get telescope running locally. We both had the same issue and we were unable to progress until we found a solution. We were contacted by Tue Nguyen who is more experienced with Telescope than us and he offered to help us through our issues. We got into a call together and set up Telescope together so we can understand where we messed up. That's where we found out that the issue was that we modified the configuration file which caused the issues.
So that's what I decided to do I wanted to improve the environment-setup documentation to prevent further errors for new telescope developers. I made sure to tell people about the bug and how to fix it.
My initial plan for the contribution was much larger but I think that supporting telescope and making it easier for new people to work on means that it will continuously improve.
What I did for the vs-code extension
I was looking over some of the new projects and I stumbled on a new project that plans to create a vs-code extension for Seneca developers. The issue was asking to add gitpod support to the vs-code extension. Gitpod allows developers to easily work in a controlled environment the gitpod.yml can automatically install what needs to be installed and run what needs to be run and it allows developers to have an easier time contributing to projects.
What this means is that I needed to read the setup doc where I researched how to set it up and how to use it for myself. I also looked at what the gitpod.yml file does and how to configure it to run a project and install the dependencies.
Top comments (0)