November 25, 2025
Stars, forks, and pitchforks
What They Don't Tell You About Maintaining an Open Source Project
From first stars to support stress, commenters split on “help them” vs “not your job”
TLDR: A solo dev says keeping a free, self-hosted app running is harder than launching; docs, support, and updates drain time. Comments split between tough-love “help yourself,” a mini platform war blaming GitHub, and “your project, your rules,” highlighting pressure on unpaid creators to set boundaries.
The maker of kaneo—a minimalist to‑do board you can run yourself—posted a reality check: shipping is easy, maintaining is hard. After the feel‑good launch came endless docs, support, and scary upgrades. He’s juggling bug fixes, “please add this feature,” and don’t-break-my-data migrations. Cue the comments: one reader swore it “sounds AI‑written,” while another went full tough love: if you won’t read the guide, don’t expect help. A platform flame sparked when a user blamed GitHub for drive‑by “how do I install?” questions, claiming other sites wouldn’t have this problem. Meanwhile, the chill crowd waved a flag for creator autonomy: it’s his project—set boundaries and move on.
There were laughs, too. Folks joked that supporting strangers through “mystery home setups” is like a video game: corporate proxies and tiny hobby computers are boss levels. The author’s fear of data‑moving upgrades (“migrations”) had readers sweating, then applauding the belt-and‑suspenders approach—dry runs, edge cases, and more. When someone tried to pin user confusion on Gen Z, another commenter shut it down with a crisp “no.” The vibe? A split between RTFM energy (read the manual), platform wars, and protect-your-sanity advice—wrapped around a very real truth: open source is free to use, not free to maintain.
Key Points
- •Kaneo is a self-hosted, open-source kanban board that gained users after its v1 release on Reddit and GitHub.
- •Documentation requires ongoing improvement to accommodate users with diverse backgrounds and assumptions.
- •User support reveals unexpected deployment environments and failure modes, informing product development.
- •Feature requests are evaluated against vision, maintainability, and complexity, with transparent communication when declining.
- •A database schema refactor was delivered with rigorous migration testing, validation, and a dry-run mode to protect data; contributions are valuable but require careful integration.