September 29, 2020
Hacktoberfest will be starting in two days, and it’s a good opportunity to get started in open-source and help out the projects you like or depend on. It’s a good opportunity because the maintainers will create a lot of issues labeled with
hacktoberfest. These are usually approachable but they all try to bring value to the project, no “please fix that typo over there”.
If you have read the 1-year anniversary blog post that I’m releasing at the same time as this post, I hope it got you excited in participating in the tool’s journey.
I have prepared a list of tasks that I think will be interesting to solve. I will create more during the course of October, including potential low-hanging ones from the other blog post, but the initial issues revolve around the same thing that got me into the realm of static analysis: writing rules.
I will be celebrating every pull request with a gif of Leonardo (or whoever you specify when making the pull request), like my pull request was when I started!
Back when I released
elm-review v2, my goal was to focus on this package right afterwards, whose aim is to make a lot of checks related to a project’s documentation and that could provide real maintenance help for package maintainers and application developers. I ended up focusing on other things, so I figured Hacktoberfest would be a good opportunity to get this project moving again.
This is the list of rules that I am proposing for Hacktoberfest (note that I won’t mention the bugs, though I would really appreciate if those were tackled too!):
masterand got removed
elm-review-unused has some issues and all of them could use some help.
There are some bugs, as well as improvements to existing rules that could report more unused code, as well as new rule ideas to also detect new code.
This package to report bad patterns around The Elm Architecture has one rule up for taking and discussing:
elm-review-common, no new rules, but it would be great if these two rules could offer an automatic fix:
These are all the issues I have been able to come up and formalize at this point. As said before, I’ll try to create more during the month. I hope you’ll find some to be interesting.
If not, you may find interesting rules in
elm-review-rule-ideas. Mention in an issue that you’d like to work on it and I’ll try to see if I can get it counted as a Hacktoberfest issue (no promises though).
There will also be a kick off event for the Elm Hacktoberfest, where you can learn more about Elm and open source, and there will be a Q & A session with Dillon Kearns (
elm-markdown), Keith Lazuka (
intellij-elm) and me.
Feel free to join the #elm-review and hacktoberfest related channels on the Incremental Elm Community Discord to ask for help!
Other ways you can help out but that won’t count for Hacktoberfest:
Thanks for reading until now, and happy Hacktoberfest!