Making my first real open-source contribution this week (Fenn ML tooling)

Hey IH,
Most of what I've shipped lately has been my own projects. This week I'm trying something different — making a real contribution to an open-source project I didn't start.
The project is Fenn — an open-source Python tool for tracking ML training sessions. The maintainer recently opened a coordination issue inviting new contributors to improve the Flask-based dashboard, and I claimed a sub-issue for [YOUR_SUB_ISSUE_AREA].
Why I'm sharing it here:

1. Public commitment. Posting it in a community I respect makes me more likely to finish the PR. Open-source intent without follow-through is one of the most common failure patterns; I want to avoid it.
2. The contribution flow is genuinely well-designed. Sub-issue first → maintainer feedback → PR linked to sub-issue. It's the inverse of the "just send a PR and hope" pattern, and it's saved me from going down the wrong implementation path already.
3. Open source is a useful counterweight to solo building. When you only ship your own stuff, you only ever encounter your own decisions. Contributing to someone else's codebase forces you to read carefully, ask questions, and write code that fits their style — all skills that compound.
   Repo: https://github.com/pyfenn/fenn
   Issue I claimed from: https://github.com/pyfenn/fenn/issues/98
   Anyone else here actively contributing to open source as a habit? Curious how you balance it against your own projects.