Hacktoberfest 2019

2 minutes

This is year number three of my participation in Hacktoberfest, the initiative from DigitalOcean, and new this year, Dev.to. In previous years, the objective was to submit five pull requests to an open-source project. This year, the number was reduced to four, for some reason.

In 2018, I submitted a total of 10 pull requests to open-source projects. This year, I did a few more than that.

#My contributions

Whilst DigitalOcean did have an official checker this year, it was pretty bad! Not only was it incredibly slow, but it was only possible to see your pull requests, rather than any user. Instead, the third-party Hacktoberfest Checker shows the relevant pull requests.

#3 Contributions to srobo/team-emails

#2 Contributions to srobo/docs

#2 Contributions to srobo/website

#2 Contributions to RealOrangeOne/zoloto

#2 Contributions to srobo/reverse-proxy

#1 Contributions to polybar/polybar-scripts

#1 Contributions to polybar/polybar

#1 Contributions to kees-z/DuplicatiDocs

#1 Contributions to srobo/inventory

#1 Contributions to aaronn/django-rest-framework-passwordless

#1 Contributions to dabapps/heroku-buildpack-cleanup


As with last year, I personally consider many of these contributions invalid, primarily because they don’t really fit with the spirit of Hacktoberfest. Namely, all those under the srobo organization don’t especially fit, and the ones on my own repos. Excluding those, there’s still more than enough to get my t-shirt!

Share this page

Similar content

View all →

Hacktoberfest 2018

2 minutes

Hacktoberfest is a great initiative created by DigitalOcean and GitHub to get more developers contributing to open-source projects. After opening a set number of pull requests to open-source projects, they’re rewarded with branded swag. As someone who does a lot of development in their free time, it’s not hard for…

Hacktoberfest 2020

2 minutes

This year’s Hacktoberfest was a little different, mostly in quite how much the internet gave a fuss about it. Given quite how much of the internet was talking about it back in early October, it doesn’t take long to find information and context on why it was so controversial. Here’s…


7 minutes

Yesterday, an email was sent to django-announce, informing of an upcoming security update, labelled “high” severity. Previous notifications like this have been one week before the actual disclosure; This email, just 12 hours. The updates were scheduled to be released 12:00 UTC the next day (today). Already, not the best…