OSS Monthly Recap: What My Daily Commit Challenge Taught Me About Open Source “Culture”

In April, while continuing my “1 Commit a Day” challenge, I submitted several pull requests to different open-source repositories.

The results were:

3 PRs submitted

1 PR merged

Contributions involving bug fixes and test updates

Some of the repositories that left the biggest impression on me were:

• Label Studio ML


• MCP Python SDK


• Hugging Face MCP Course Material

One thing I’ve been realizing recently is that open source is not just a place to write code.

Every repository has its own culture, workflow, and communication style.

For example, while contributing documentation to the MCP Python SDK repository, I initially struggled quite a bit with the pre-commit checks.

At first, I didn’t fully understand what was causing the errors, so I opened an Issue about the problem. The maintainer responded that I should not open an Issue like that since it was directly related to my PR.

At the time, I was a bit confused because no additional explanation was given, but looking back, I realized that discussions closely tied to a PR are generally expected to stay within the PR conversation itself.

Looking back, that makes complete sense.

Keeping the discussion connected to the PR preserves context and makes things easier for maintainers to manage.

It was a small interaction, but it taught me something important:

In OSS, communication is just as important as technical skill.

I also gained a much better understanding of what pre-commit actually does.

Before this, I mostly thought of it as “something that automatically runs checks before commits.” But through the contribution process, I started to understand how it helps maintain:

• code style


• formatting


• linting


• overall project quality

When I first started my daily commit challenge, my goal was simply:

“stay consistent.”

But recently, I’ve started enjoying something else:

slowly learning how different OSS communities work and how real collaborative development happens.

My goal next month (May) is to increase my Level 3 contributions and continue improving both technically and collaboratively.

One thing I’m learning is that contributing to open source is not only about writing code — it’s also about learning how to work with people, processes, and project culture.