GoKawiilThere’s a particular kind of sinking feeling you get as a user of open-source software. You’ve built your setup around a tool you love, it does exactly what you need, and then you notice the last commit was eighteen months ago. The issues are piling up. A platform update breaks it. And the maintainer, understandably, has moved on with their life.
Six years ago I hit exactly that wall with a Home Assistant calendar card called Atomic Calendar. I had two choices: rip it out of my dashboard and find something else, or roll up my sleeves and adopt it.
I picked the second one. That decision became Atomic Calendar Revive, and today it sits at 629 stars, 79 forks, and somewhere north of 1,700 commits, installed on dashboards I’ll never see all over the world.
This isn’t a tutorial. It’s the honest story of what it’s actually like to inherit, revive, and keep a popular open-source project alive for half a decade, and what it taught me as an engineer.
What it is (the 30-second version)
Atomic Calendar Revive is an advanced calendar card for Home Assistant’s Lovelace dashboard. It pulls events from Google Calendar, CalDAV and any HA calendar entity, and renders them as either an agenda-style event list or a full month view, with a ridiculous number of configuration options and a visual editor so you don’t have to hand-write YAML. It’s TypeScript, built with Rollup, and distributed through HACS.
That’s the what. The interesting part is everything around it.
Lesson 1: a fork is a commitment, not a weekend project
When you fork an abandoned project to “just fix the one thing that’s broken,” you are quietly signing up to become its maintainer. The moment you publish that fork and a single other person installs it, you own their experience.
I didn’t fully appreciate this at the start. The first few weeks were genuinely fun: fix the breakage, tidy some code, ship a release. Then the issues started arriving. Not because I’d done anything wrong, but because a working project attracts users, and users find edge cases you never imagined. Different calendar providers, time zones I’d never tested, locales, themes, devices.
... continue reading