Skip to main content

DPS 909 - Release 0.3 - Diving Deeper

Hacktoberfest has come and gone. For everyone who attended and made an effort... hopefully you all got your shirts! For the rest of us... well you win some and then you lose some. But if you didn't, don't let it get you down - the true open source is the friends you made along the way. And speaking of friends, our Fall 2019 class of DPS 909 at Seneca College has decided to do something a little special for our Release 0.3 assignment: we've started our own internal, open source project!

To cut a long story short, we've been tasked with developing a web application that aggregates open-source-related blog posts from current and former students of the DPS 909 course. A very old, and very out-dated version of the website current exists here, but it is clunky, buggy, and prone to errors that block up the whole system. It's our job as the current students of DPS 909 to redesign and revitalize this website into something much more intuitive and robust. The repo of our current project can be found here.

We can do better!
With 60 students currently enrolled in the course, we are in no shortage of contributors, but organizing a project around that many amateur open source developers is a task in and of itself. It's been about a week and a half since the project was announced, and already there was quite a bit of learning involved. We've had to slowly grasp how to take charge of issues; on top of actually writing code and submitting pull requests to the project repo, we also have to take part in discussions regarding the development of the system itself, as well as review our peers' contributions. Unsurprisingly, it's been quite a hectic experience, but also a valuable learning opportunity! You can find the full project description here, along with our list of MVP features and future pipe dreams... hopefully we'll make it work!

As for my contributions, I've been doing a lot of learning, as well as passing off what I've learned to the team via our project discussion boards and Slack channel (the latter of which is private... sorry!). For example, in order to get the project rolling, I suggested we implement a simple plaintext website that simply retrieves blog content and caches them as JSON files - a system that would make up a very rudimentary backend until a proper database can be implemented. I don't know if my suggestion made a difference or not, but our instructor, David Humphrey, went ahead and developed a basic system that retrieves blog URLS from a plaintext file and logs the queue to console (thanks Dave!).

I am currently working on implementing a way to retrieve blog posts from RSS and Atom feeds, and filtering them based on the timestamps of the blogger's most recent post. The idea is that we don't want to keep displaying outdated blogs that are no longer maintained by their authors, or, at the very least, mark them as being on hiatus. As I develop my contribution, I am keeping in mind that eventually it will make its way into a system that is being worked on by dozens of other people. So, modularity is key, which is great news considering we're working in Node.js!

Before I've even started laying down any code, I've already run into something of an issue. The containerization platform we've chosen, Docker, does not play well with VirtualBox, which I need installed on my workstation for another school course. Looks like I'm going to have to do some native installations.

Uh oh.
Aside from the internal project, we're also required to continue our contributions to external open source endeavors. I have not began my work on any external projects just yet for Release 0.3, but I've definitely scoped out the project I want to work on - the open source game engine Godot. I've used the Godot software for some hobby-grade game development in the past, so I think it's high time I contributed back to the community! There are as many as 5000+ issues currently at large... choices, choices!

No shortage of issues on the Godot game engine project.
There's definitely lots to work on these coming weeks, so stay spry and keep hydrated folks!

Comments

Popular posts from this blog

DPS909 - Lab 1 - Github Trending Research: WebGL Fluid Simulator

The WebGL Fluid Simulator is a small application that allows the user to play with simulated fluids right in their browser, and works on both PCs and mobile devices. The visual effects follow proper fluid dynamics, and can be manipulated in real time by pointing and click, as well as several available options such as quality, density, and velocity.  The app is written in JavaScript, and as the name suggests, visually renders its effects using WebGL. It was created by Github user PavelDoGreat based off another Github project:  Fluids-2D , and is distributed under the MIT license. As of September 8th, 2019, WebGL Fluid Simulator is trending with 2,307 stars during the month, and 6,070 stars in total. Main interface of WebGL Fluid Simulator by Github user PavelDoGreat I was interested in investigating this project as it demonstrates the breadth of open source resources on Github. Users can find projects that range from complex systems and APIs, to small plug-ins and simpl...

DPS 909 - Release 0.2 - Hacktoberfest Week 4

It's the home stretch for Hacktober fest! For my final contribution, I decided to tackle my last goal , which was simply to do something fun and interesting. Once again, thanks to GitHub user vichitr and his brilliant project , I was able to quickly find something to contribute. I've always thought that programming algorithms was a good challenge and invited great learning experiences, so for my final PR, I decided to program an example of the sliding window technique in Python. The sliding window technique is a very useful algorithm that is used across many disciplines of software design. It allows users to compare subsets of data (i.e. windows) within a larger collection, in order to find significant items. Personally, I have encountered the sliding window technique during some applied research projects that I have tackled in the past. In a particular machine learning project, I used the sliding window technique to construct subsets of data that were then fed into a separa...

DPS 909 - Release 0.4 - Quick Weekly Recap

Last week , I talked about my external contribution and the trouble I had with setup. This week, I performed my contribution to our internal project: Seneca Telescope . I wanted to work on an aspect of the project that I had not dabbled in before, so I chose to restructure some code in order to create fixtures. So here's a quick recap of the work I did for this week's release 0.4 contribution. Internal Contribution - Adding Fixtures to Telescope In this context, fixtures refers to elements in a software project that are used to create a reproducible testing environment. In the case of project Telescope, there are certain components of the web app that parse RSS and Atom feed URLs in order to derive the contents of a blog. In order to test these components, we created a "dummy" blog account that produced a very specific feed output when parsed. Since we know what output to anticipate, we can use the dummy blog to test the various parsing components of Telescope. ...