Disclaimer: The community event ended two years ago in October, but my first dev swag was just delivered to me a few business days ago.
March 29, 2019
March 4, 2020 — 17:34
Hacktoberfest motivates newbies to contribute to open source projects. In case you need to know, last year was my first time participating fully, and I did not regret a minute of it. Although come to think of it now, there were a few things I could have done to maximize my participation.
If you’ve been thinking about collaborating with others, open source is a great start. Every year since 2013, the community celebrates open source software by rewarding contributors during the month of October.
Don’t worry so much about the coding bits, because the focus of Hacktoberfest is *to contribute to a software project*. It is first-timer friendly, and you are not limited to only your coding skill sets. Any area where you might be able to help is within your reach: social media marketing, copywriting, editing, design, testing, bug reporting, business, etc.
Okay, maybe business is still a little way off, but here are some things you can do to get started (right away):
1. Check for broken and/or outdated links. This is mostly what I did. I contributed to a WebDevStudio project creating WordPress starter themes, so there were plenty of links referencing WordPress’s Codex, which has moved to a different subdomain but still at Wordpress.org. Some of these links are not broken; they simply need to be updated to point to the most recent webpages.
2. Fix the typos. Typos are bugs! And you need to fix them. Content can be buggy, too, especially if the website is localized into other languages. Go for the obvious grammar and misspelling ones, rather than the more subtle issues of style.
3. Make sure the viewport is for responsive pages. Modern websites are built with mobile in mind, so they've got to be responsive and stay responsive. You should be able to go over the website code and check if the viewport meta tag is correctly set up.
You can (and you should) copy your projects's URL and paste it on to any mobile SEO tool to check for things like the viewport tag, load time, image optimization, etc. is correctly used. If the viewport is not, for example, responsive, that could just be your very first PR.
Luckily, I have read about how to make a Pull Request/PR years back when I first learned to use Git and GitHub. So I wasn’t all that unfamiliar with the way open source projects work, but like I said, it was years ago. To make your first real PR, you need to learn to create a PR on GitHub. And you need to practice.
There’s a bunch of very neat tutorials from Hacktoberfest’s host, Digital Ocean. I encourage you to go to their website and read their Introduction to Open Source thoroughly before installing Git on your computer. Follow the Git installation guide there, too.
But if installing Git looks like a lot of extra work, you can definitely skip it. There are open source projects, such as the freeCodeCamp repository, that will let you help improve articles by editing directly from your browser.
Learning about open source projects and how to contribute is only the beginning. You still need to find projects you can actually contribute to. Many are reserved for first-timers to take part in during the Hacktoberfest community event. And if you do a bit of internet search, you will find many such project lists.
Just need to do some digging to find those repos.
These are some other interesting first-timer guides to open source projects. Each includes links to where to find your first:
As you can probably imagine, getting started is easy as 1-2-3:
1. Before registering for Hacktoberfest, you need to setup a GitHub account that you’ll use during the community event. You can do that from GitHub: github.com/join.
2. Register through the Hacktoberfest registration page.
3. Make 5 PRs and follow the instructions to receive your dev swag.
But if you tried to contribute to these open source projects outside of Hacktoberfest it would have taken you some time, and probably more than 5 issues, before your contribution is considered "good enough." After my first contribution in 2018, I still return to the projects to see how else I can make myself useful. So here's some of my after thoughts:
If your project has a mailing list, you should definitely join it. In theory, reading up on the project’s reporting guideline, Slack channel discussion, and developer forums would help you select a decent issue to work on. The project’s contributing guideline also would lay out the basics to help you prepare your PRs.
This is hard. But it’s one of the main benefits of working on open source projects: you get to work with other developers. When you need (and you will need it) some help, you should ask for assistance from other developers and communicate. This ensures that you are able to work on the items you have set out to work on. They can point you to the right direction or advice you on where to look for stuff.
Turns out that the open source community has a culture of rewarding contributors with swag! Each of the companies have their own requirement for the free gifts they give for your time and your help. Why not make the most of your contributing month? During Hacktoberfest, try to contribute to the companies that offer dev swags. They could also motivate you to continue contributing regularly to projects that match your schedule and qualifications.
If existing projects are no longer sufficient, you’d want to consider creating your own. With the right dev swags (and marketing mix) you might be able to attract rising talents that could lead to somewhere amazing.
This issue has come up in online forum discussions. After some time, the package tracking for Hacktoberfest swag became unavailable.. so people weren't able to find out where their package was or where the rewards got stuck. I was told that my package was already dispatched in time but was rejected due to conflict of address. The design team had to resend my package, and luckily the second time was a charm.
Indonesian customs fee for imported goods does not charge any item that is less than $100 in value, but somehow my dev swag was held in customs, as proven by the customs tariff receipt handed to me. I had to pay about $1.5 for customs, which is hilarious! The package itself is not even a taxable item. It took my swag about one month to make it to the post office.