Skip to content

Question on finding early contributors for the OSS kit #1

@flyoung588

Description

@flyoung588

I was reading through creatorem-saas-kit-oss and noticed the split you’ve made between the OSS baseline and Premium: dashboard app, analytics, monitoring, i18n, and AI chat UI in OSS, with billing/orgs/CMS/mobile/examples kept out. The CLI-first setup via npx @creatorem/cli create also seems like an important design choice, since it makes the kit more than just a repo clone.

One outside observation: for a project like this, the hard part may not only be deciding what belongs in OSS vs Premium, but finding contributors who care about the exact stack and product shape — TypeScript, Next.js, Supabase, Turborepo, SaaS-dashboard primitives — before the repo has much visible issue activity.

I’m Ray, a founder working in an adjacent space. This is a genuine question, not a pitch.

For an OSS SaaS kit at this stage, have you already tried to find early contributors manually — through GitHub, X, Discord, friends, customers, etc. — or is contributor growth not something you’re spending time on yet?

A short reply is plenty.

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