Exploring the Open Source Realm

Last week in my blog i mentioned working on integrating Lighthouse CI into our course project . The goal was to provide a tool for contributors working on the front-end side of the project. With lighthouse, our contributors could run some diagnostics test to know which parts of the front-end could be improved upon. So for the last week, I have been reading documentation and blogs/articles for lighthouse ci. One of the things i picked up was that for a future project i could use lighthouse ci and integrate it with my server, and also i can use Github Actions to automatically run diagnostics and produce reports. But this wasn't the solution we needed for our course project. So i came across the CLI documents . With the Lighthouse CLI, I would be able to set up it up and test the files locally. Using npm i installed the API: npm install -g @lhci/cli Afterward, i used collect the run the diagnostics tests and store lighthouse reports in the .lighthouseci/ folder. Usi

For the next couple of weeks, i will be focused on my internal pull request. My task is to work with Lighthouse CI  and try to implement it into our course project the telescope . I can predict that this will be very fun and at the same time very challenging. But with research and experimenting, I'm sure i will figure out the most suitable way. Lighthouse CI is a tool developed by Google to allow developers to test their websites and based on results given by the tool, improve their website. Implementing this would help us improve the front-end side of the project. As of now, I haven't found anything to work on for my external pull request. I'm still in search of something I could do with TypeScript. I also have to address my vscode pull request which i talked about last week.

In my last week's blog, I talked about the two objectives I would take on during November. In the middle of working on the contributions, I decided to change my issue for the internal open source project. I'm hoping to continue with this issue for next pull request I have to submit for my course. As you know, the external open source project I chose to contribute to was vscode . In the beginning, when i saw this issue , i thought this would be an uncomplicated and straightforward issue to work on within a big open source project. Before i forked the clown, i took a good look at the documents they had to just get a sense of how to contribute to the project and do the simple tasks of running and testing. After cloning, i had an issue running the project, this is where i spent some good time reading the documentation again, but i was just having a hard time running the project. I managed to get it running after a few reads.  Thanks to another contributor i had a hint of where

November is upon us and its time to take it up a notch. I have two objectives to focus on during the next week: Contribute to an external open source project  Contribute to an internal open source project run by my classmates For the external open source project, I chose to contribute to vscode . Personally, I use visual studio code and being able to get involved is very electrifying for me.  After looking through the issues on the project, I found this issue . With the help of another contributor, I got a sense of direction of where to tackle the issue. For the internal open source project, our class is responsible for redesigning the Planet CDOT  where it tracks and displays blogs of students and their participation in open source. I had my mind on learning new technology and i was circling around doing some with Continuous Integration and Continuous Deployment. I decided to help another classmate set a pipeline for CI/CD with Jenkins. Collaborating with someone on th

The last day of Hacktoberfest is here and I submit my last pull request. It has been a great exposure to the open-source community. Before starting hacktoberfest I set two goals: Git - How to use git C# & TypeScript - Learn new languages Working with multiple projects, I managed to get a hang of using git. Unfourtonalty I didn't have the chance to give C# & TypeScript. My plan is to focus on this goal for the next month as we dive into working with big open source projects. rhymus This week I had the opportunity to work on rhymus .  the bug was to display the score to the player once the game was over. At first, the developer wanted the score to be displayed in a pop-up. I tried using javascript alert() method on but it didn't look very user-friendly, so I decided to come up with a design and suggest it to him. I decided to add the scoreboard on the card once the game was over and would be removed for a new game. Afterwards, I made the pull request and

Wow! The third week of Hacktoberfest is coming to an end and it has been an experience for me so far. Before hacktoberfest, I never thought that I would be able to contribute to other people's projects and actually see my contribution be committed to a project. This week was a huge step for me. I had to opportunity to work on a project that I found very interesting and test my coding skills with the application. The best part of the experience was that it gave me the chance to collaborate on the issue with the main developer where we discussed how to come up with a solution. After the solution was provided, my code was merged into the main project which gave me a sense of accomplishment and satisfaction,. The Project After countless hours searching through GitHub for an open-source project to contribute to, I came across Time to Leave  developed by thamara. This application is like a reminder that allows users to log their work hours it the application and receive a notificat