Hacktoberfest Recap: Open source Ruby/Rails work in 2020
Tags: ruby, rails
Published: 2021-02-12 02:53:10

---
title: Hacktoberfest Recap: Open source Ruby/Rails work in 2020
published: true
date: 2020-11-16 13:00:00 UTC
tags: ruby,rails
canonical_url: https://boringrails.com/articles/hacktoberfest-2020-recap/
---

[Hacktoberfest](https://hacktoberfest.digitalocean.com/) is a month long event that encourages developers to contribute to open source – submit four valid pull requests and you win a tshirt. Despite the [criticisms and controversy](https://joel.net/how-one-guy-ruined-hacktoberfest2020-drama) this year, I’m a fan of the event and it did help motivate me to make some contributions.

I wanted to share a recap of my submissions for Hacktoberfest because I think it’s a good sampling of what options are available to folks looking to contribute to Ruby and Rails. There are lots of ways to give back outside of the main `rails/rails` repository!

![My 2020 Hacktoberfest Contributions](https://boringrails.com/images/hacktoberfest-2020.png)

## ViewComponent

Repository: [`github/view_component`](https://github.com/github/view_component/pull/493)

Pull request: [Allow preview controller to be customized via config options](https://github.com/github/view_component/pull/493)

The `view_component` gem helps you organize your server-rended view partials into “components” that are backed by a Ruby class. If you’re familiar with the built-in Rails `partials` and gems that implement decorator or presenter patterns (like `draper`), you can think of `view_component` as a mash-up of those two approaches.

I’ve been playing around with this gem on my own projects and think it’s heading in a great direction. I found an existing [issue](https://github.com/github/view_component/issues/434) with a “help-wanted” tag and decided to see if I could add the feature.

The `view_component` gem allows you to test out your components in a sandbox mode (akin to Rail’s `mailer` previews). There was a feature request to support customizing the controller used to render these previews in case you want to add authorization or other special application-specific things.

The pull request was merged and release in [version 2.20.0](https://github.com/github/view_component/blob/master/CHANGELOG.md#2200)

Gems like this are a great starting point for contributing. You certainly have more experience using a gem in your own application than working deep in the Rails internals so adding features or fixing bugs in a gem will be more approachable.

It was extra helpful that the maintainers tagged issues with “help-wanted” and there was low enough “traffic” that I was able to get questions answered and my code reviewed very quickly.

## Bullet

Repository: [`flyerhzm/bullet`](https://github.com/flyerhzm/bullet)

Pull request: [Update design for footer notification](https://github.com/flyerhzm/bullet/pull/522)

The `bullet` gem is one of my go-to tools when building Rails apps. This gem will flag N+1 queries as you’re developing a feature and alert you to associations you should preload. It’s a lot nicer to find and stamp out these performance problems as you go instead of months later when they appear in production.

You can configure how `bullet` notifies you of problems. My default preference is a browser popup – it’s annoying but it does drive me to fix the problem instead of ignoring it. But sometimes there are false positives or I’m prototyping a feature and it becomes too much. So I went to switch the configuration to use the “footer” where it would add a banner to the page with the error message.

But I really disliked the design: it took of a ton of space and was, well, ugly.

So I decided to change it. You can see the “Before” and “After” [here](https://github.com/flyerhzm/bullet/pull/522#issue-495898756). The new design is expandable and gets out of the way.

The pull request was merged and will be included in the next release of the gem.

## LRUG

Repository: [`lrug/lrug.org`](https://github.com/lrug/lrug.org)

Pull request: [Add link to StimulusJS talk slides](https://github.com/lrug/lrug.org/pull/130)

[LRUG](https://lrug.org/) is a local Ruby meetup group in London. While this contribution on GitHub was tiny (merely updating their website with a link to the slides for a talk I gave), it’s still an example of how to contribute to the Ruby community.

Meetups are always looking for volunteer speakers and given that many groups are doing virtual meetups in 2020, I thought it might be fun to branch out from my local meetup (Indianapolis) and offer to speak at two groups in Europe. I gave a talk about using StimulusJS to the [Berlin Ruby user group](https://www.rug-b.de/events/ruby-usergroup-berlin-september-2020-637) and the [London group](https://lrug.org/meetings/2020/september/). It was cool to be an “international speaker” and I was able to take advantage of the timezone difference to simply slot the presentation into my normal workday calendar (lunchtime in the US is evening time in the EU).

Overall I had a great experience and a warm welcome from my new Ruby friends on the otherside of the world.

## Ruby For Good: Circulate

Repository: [`rubyforgood/circulate`](https://github.com/rubyforgood/circulate)

Pull request: [Add power source field to items](https://github.com/rubyforgood/circulate/pull/257)

I came across the [Ruby For Good organization](https://rubyforgood.org/) when looking for projects to contribute to and found that they manage a number of [Ruby and Rails projects](https://github.com/rubyforgood) that help non-profits that need software development work done. There are apps for helping with conservation, diaper banks, volunteer management, and more.

I found a project that is building an inventory management system for tool-lending libraries. The idea is that you can borrow tools from a community pool or schedule time to use machinery that is usually too expensive for an individual to own themselves.

The Ruby for Good projects seem to all have a team of people to help triage and define work items and there is a Slack channel to coordinate and ask questions. I thought it was really neat to be able to contribute to an open source project where you were writing features like most developers do as part of their “normal” job. Writing frameworks and libraries is critical, but it takes a different set of skills and mindset than doing application development.

I was able to get the project up and running locally in under an hour and I banged out a feature to add a new field to `Item`s in the system to record what kind of power source the tool uses.

The pull request was merged and deployed to the [Chicago Tool Library](https://app.chicagotoollibrary.org/) app.

## Wrap it up

Despite the flaws and issues with incentives, I find Hacktoberfest to personally be a very motivating effort. There are several ways to contribute to the Ruby or Rails open source ecosystems – even if you aren’t keen to dive into a huge framework or project.

You can start by looking at some of your favorite gems and see if there are improvements you can make – after all, your perspective as an end-user is invaluable.

Consider giving a talk at a local (or remote!) user group. No matter how far along in your programming journey you are, you can always share something about what you’ve learned that can help someone else.

And lastly, consider checking our Ruby for Good if you’re looking to practice more of the day-to-day Rails development skills. These projects seem like a great environment for junior developers as they have dedicated folks involved to help review code and write feature specifications.

Did you complete Hacktoberfest? If so, I’d love to hear about your contributions on [Twitter](https://twitter.com/_swanson).

* * *
[![](https://boringrails.com/images/twitter-banner.png)](https://twitter.com/_swanson)