Open Source blog

In the third release, I was working on the  Vibranium GitHub project. Setting up a project on my machine took me a while, but was useful in terms of getting familiar working with Firebase which I never used before. Firebase is basically a mobile and web application development platform. In order to get the project working, I had to install node, run " npm install " and install firebase using " npm i -g firebase-tools "  command. In order to host your project using Firebase, you first need to create a Google Firebase account and then create a project on their official page. After doing that, login into your account from the terminal using " firebase login " and run " firebase init " in order to create firebase.json file. Add a project from firebase console using " firebase -add project-name " and finally publish it with " firebase deploy ". The issue I picked was to create a custom 404 error page when the server is unabl...

For the third release, I was looking into a bunch of different tickets, but it turned out to be quite hard to find a good one. Some of the tickets I found were still open, but already fixed in the code, others required more info to start working on them, and I couldn't get any response from the team. For now, I ended up looking into Marquez  project. It has a lot of nice tickets, but I'm still having troubles to get it working on my machine. Other tickets that I consider working on are: https://github.com/natlas/natlas/issues/113 https://github.com/Marko-Doornbos/tournament-site/issues/12 https://github.com/ICT4Dat/ict4dat-news-android/issues/159

In the third release, I'm planning to work on one of my previously selected projects. From my experience with popular GitHub open source projects, sometimes it might take a lot of time to get any reply from their team, which might be a problem if I come up with any questions along the way. Moreover, picking a project from the previous release will save time on setting up the project and getting familiar with it. Slothpixel project One of the good options to work on in the next release is Slothpixel project. It is an open source Hypixel data platform which is currently at the early stage of its development. It uses React JavaScript library to build user interface. React is considered to be one of the most demanded programming skill in the job markets and one of the most popular javascript frameworks. So it will be a perfect add-on to my resume. The issue I might work on: -  https://github.com/slothpixel/ui/issues/3

The second release was very useful in terms of learning how to work with git commands and how to find, setup and contribute to a bunch of different open source projects. As it turned out, the hardest part of the whole process for me was setting up a new project on my machine. Some times you can't manage to get a part of the required technology to properly install and work, other times something that is already installed on your machine interferes with new stuff. Eventually, you might end up spending more than 3 hours just to get everything working, and submit your pull request only after a few minutes of working with actual code.  Another issue of working on open source projects is the complexity behind finding a good bug that you can take over and work on. Some tickets lack a good description, some don't have any at all. Looking for a good issue to work on, you can discover that the project doesn't have any documentation and most of the time you can neither understand wh...

On the fourth week, I was working on the same project as on the previous one, called  Marquez . For my last PR I was doing some code cleanups marked with "good first issue" label. This time the main task was to add some cleanliness and consistency to the code by changing all variables referencing "Datasets" to use the same style and format. As I already had the project installed on my machine, it was a pretty quick fix. Using Visual Studio Code search function I was able to find all mentions of "Datasets" in all project's files. A very useful thing for my search was finding the Match Case (Alt+C) function that is located right beside the search field. This function allowed me to perform a case-sensitive search, only displaying the relevant results. My Issue: https://github.com/MarquezProject/marquez/issues/350 My PR: https://github.com/MarquezProject/marquez/pull/362