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 some useful links to find out a little more:
I don’t envy the organizers of Hacktoberfest this year. They’ve taken a lot of fire for what’s meant to be an honest event to get people interested in contributing to open source. It’s just a shame a few members of the community helped ruin it for so many others.
Personally I dislike the move to opt-in, I’d have preferred to see an opt-out. This way even idly maintained repositories could have still seen a benefit.
This year, my contributions can be split up a little. I created a number of open-source PRs in October, but only a small number (☑️) were actually valid by the new hacktoberfest rules.
ajalt/fuckitpycarltongibson/django-filteris_valid to raise a validation error when invaliddabapps/django-enforce-hostdabapps/django-s3-file-upload-serverdabapps/django-zen-queriesplausible/analyticsselfhostedshow/halcyonselfhostedshow/homeassistant-rssrobo/team-emailssrobo/volunteer-emailssrobo/websiteyarnpkg/websiteWill Hacktoberfest 2021 continue? Or will the curse of 2020 claim another victim?
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…
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…
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…