Skip to content

Question on finding early contributors for Doable’s deployment-heavy surface area #51

@flyoung588

Description

@flyoung588

Hi — Ray here, a founder working in an adjacent devtools/open-source space. This is a genuine question, not a pitch.

I was reading through Doable and noticed how much of the early surface area is operational, not just “AI app builder” code: the bash + native PowerShell setup paths, Caddy-in-Docker TLS with mkcert, the VPS quickstart, Cloudflare-managed domains, plus deploy targets for Render/Railway/Heroku/Fly/K8s/Coolify. That feels like a lot for an early TypeScript project to keep coherent, especially alongside multi-tenancy, sandboxing, audit logs, MFA, and RBAC.

One outside observation: the repo seems like it will need contributors who are not just React/Next.js people, but people comfortable with self-hosting, Docker, Windows edge cases, and deployment docs. Those are often harder to find because they do not always show up through the usual “good first issue” path.

My question: for a project like Doable, are you already doing anything manual to find those first few contributors — posting in communities, reaching out to people from similar repos, asking users directly — or is contributor discovery not yet a real pain for you?

A short reply is plenty. I’m mainly trying to understand how this looks from the maintainer side at this stage.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions