Niko

Posted on May 26

Contributing Upstream Instead of Forking: My grape-swagger-rails Story

#api #opensource #rails #ruby

Recently I had a chance to contribute to grape-swagger-rails, helping modernize the project and release v1.0.0.

What started as a small fix turned into one of my favorite open source experiences.

The Problem

At the time, grape-swagger-rails was still using a very old Swagger UI (v0.7.0).

The UI looked outdated and lacked many modern Swagger/OpenAPI features developers expect today.

Even the interaction model and styling clearly showed its age.

In many companies I worked with, the usual approach for issues like this was:

Honestly, that's often the fastest short-term solution.

But this time I wanted to try something different.

Instead of maintaining another private fork, I decided to contribute directly to the project.

I reached out to the grape community and started working with maintainers, especially @dblock.

Together we:

That work became:

The project now ships with a much more modern Swagger experience.

Compared to the old endpoint rendering:

One thing I definitely didn't expect when opening my first contribution was eventually becoming part of the grape team.

That was honestly a very happy moment for me.

This experience reminded me that contributing upstream can have a much bigger impact than solving problems only locally.