Joel's Open Source Dev Blog

This will be my last post written for my OSD600 course, after that, every post will be about my own journey in programming. And so I wanted to say that this course, out of all the classes I've taken so far in Seneca College for my program (CPA), is by far the absolute best course I've had in the school. The topics it covers, the knowledge it teaches, and the practicality of it is just exceptional. I've learnt so much from this course, from both the professor and my own, and that's thanks to Prof. David Humphrey's mentoring. He not only taught us how to use GitHub, make pull requests, and use Git, which I should mention is one of the most well taught guides on how to use it and I recommend anyone to watch his recorded lectures on his YouTube channel , but he also taught us how to go out on our own and expand our knowledge through the beauty of Open Source Programming. With this newfound knowledge I've acquired from the class, I'm much more confident and eager

So for the past week I've been working on and off with migrating the components for telescope I've taken from the list that needs porting.  The Components I've undertaken are BackToTopButton GitHubContributorCard DynamicImage I was hoping to work on one of the Search components since I've spent so much time previously working on them, but it looks like some of my other peers have already beat me to it. Nevertheless, I still wanted to help with the migration as much as I can. So I used this  reference our professor had posted in the Meta issue regarding migrating from Gatsby to Next JS. The first thing to do is to edit the dependencies in the package.json, since it's different than the one used for the Gatsby front-end. We will still need the Material UI modules for our front end, but all the gatsby dependencies will now be removed in place of something else. For example, the Image component used from gatsby-image will now be replaced with next/image. Where as in bu

So this past weekend, I've finally released the CLI tool we've been working on this whole semester for its first offical release! linkChek 1.0.0 is up on npm and GitHub! Last week we were tasked by our professor for our final lab, to release our CLI program that we've been gradually working on throughout the labs for this semester and polish it up for production. So as a Node.JS app, I had to look up how to release my program on the npm registry. The process was quite simple. I just had to edit the package.json file a little bit with info such as keywords for the npm database, final name for release, and github repo links, just to name a few.  So I pushed my final commit on the master branch for the release, added the 1.0.0 tag and followed these instructions to publish an unscoped package up on npm website. Now you can install and run linkChek with this command in your shell npx linkChek or npm install linkChek Here is the page on the NPM website : linkChek [ https://www.

So since 2 weeks ago, we've been tasked to start working on our final release 0.4 assignment which is to make a real meaningful contribution , bigger than our previous releases,  to any repo of choice. So the first week was generally spent conceptualizing and searching for a repo of choice, while the second week was to start working on it. Next week we are expected to make our finishing touches to the release. The requirements of the release are pretty ambiguous, since our prof mentioned it can vary from to contributing to a number of bug fixes, or a a large feature addition, but the main point is to really dive deep into a repo to understand and help in pushing the program/app forward. Last week I dove into GitHub explore to look for repos that I may contribute to, and I have to say, it was much easier back in October when people were generally welcoming and looking for open source contributions from a variety of programmers. Now, though a large number of issues still exist in the