I noticed open-kanban is already set up in a pretty contributor-readable way: small Preact + Hono + SQLite stack, explicit src/server / src/client split, schema in schema.sql, and the ?agent=true UI path for browser automation instead of relying only on drag-and-drop.
One outside observation: the repo feels more “ready to extend” than many small app-template repos, because the README names the moving pieces and the product surface is concrete. If I were looking for first issues, I’d expect things like labels/card metadata, project switching, auth boundaries, or import/export to be easy to explain.
I’m Ray, a founder working near open-source devtools/recruiting. This is a genuine question, not a pitch.
For open-kanban, if you wanted your first outside contributor, would the harder part be defining a useful first change, or finding/reaching the right person to take it on?
A short reply is plenty.
I noticed
open-kanbanis already set up in a pretty contributor-readable way: small Preact + Hono + SQLite stack, explicitsrc/server/src/clientsplit, schema inschema.sql, and the?agent=trueUI path for browser automation instead of relying only on drag-and-drop.One outside observation: the repo feels more “ready to extend” than many small app-template repos, because the README names the moving pieces and the product surface is concrete. If I were looking for first issues, I’d expect things like labels/card metadata, project switching, auth boundaries, or import/export to be easy to explain.
I’m Ray, a founder working near open-source devtools/recruiting. This is a genuine question, not a pitch.
For
open-kanban, if you wanted your first outside contributor, would the harder part be defining a useful first change, or finding/reaching the right person to take it on?A short reply is plenty.