Planning to open source Voiden (https://voiden.md/) soon.
This isn’t a “maybe someday” idea anymore, it’s a deliberate step we want to take in the coming weeks.
We started Voiden as a tool we wanted for ourselves: a minimal, offline-first API client that works with plain text, no accounts, no cloud sync, no SaaS gravity. Just something that respects how developers already work.
Open sourcing feels like the right next move, but I’ll be honest: it also raises a lot of questions for us.
We have talked to many devs who strongly believe tools like this should be open. At the same time, we are thinking carefully about:
how to structure the repo and contributions
how to balance direction vs community input
what we wish we had known before flipping the switch
etc etc.
So I wanted to open this up and ask directly:
If you have open sourced a project (especially a dev tool):
What do you wish you had done differently at the start?
What mistakes are common but avoidable?
Anything you underestimated, emotionally, technically, or community-wise?
Any advice you’d give before making it public?
I want to stay committed to doing this thoughtfully, not performativel, so learning from people who have been through it already would help a lot.
Appreciate any hard-earned lessons you are willing to share 🙏
Top comments (0)