Open-Source Marketing — 0 to 60K GitHub Stars

Key takeaways

Stars follow placement and order, not repo quality alone — sequence the channels.
English > multilingual > Chinese-only: launching an English project to Chinese communities first wastes your best shot.
Show HN is not a one-shot — Tuesday 9am ET or Saturday, then engage every comment for the full day.
Never farm stars — GitHub detects it fast and the penalty is disappearing from search.

What this is

Stars don't come from a great repo — they come from a great repo placed in front of the right developers, in the right order. This is the exact staged decision framework used to take AFFiNE from 0 to 60K stars, with 10K reached in 43 days.

Key results

AFFiNE GitHub stars (24 months)	60,000+
Time to first 10K stars	43 days
GitHub Trending appearances	28×
Dev-tool startups advised	150+

The 3-stage open-source growth framework

1
Stage 1 · Pre-launch (T-30 → T-0)
Get the README English-first and readable in under 3 seconds, ship a captioned 60-second demo, choose your license deliberately (MIT / Apache-2 / AGPL each carry traps), line up 3–5 early contributors, and open an English-first Discord or Telegram.
2
Stage 2 · Launch (T-0 → T+14)
Run the Product Hunt sequence, post Show HN (Tuesday 9am ET or Saturday), seed 3 relevant subreddits, publish deep technical posts on dev.to / Zenn / CSDN, and line up 3–5 KOLs (activity beats follower count).
3
Stage 3 · Growth (T+14 → T+180)
Ship one technical blog per week, turn GitHub Issues into FAQ content, send a monthly update to the mailing list + Discord, and localize for Japan/Korea first when going global.
4
Sustain · the monthly loop
Keep a 300-stars/month cadence: weekly content, Reddit 2–3×/week, a monthly AMA, and 10+ Good First Issues so contributors compound the growth.

Launch channels — what each is good for

Sequence channels to their strengths; don't spray the same post everywhere on day one.

Channel	Best for	Note
Show HN	Credibility spike + dev traffic	Tue 9am ET / Sat; engage all day
Reddit (3 subs)	Targeted developer reach	Post once per sub, never drive-by
Product Hunt	Broad visibility + social proof	Run the dedicated launch sequence
dev.to / Zenn / CSDN	Long-tail SEO + discovery	Deep technical posts, weekly

Anti-patterns (the things that get you un-discovered)

Farming stars — GitHub detects it fast; the penalty is disappearing from search.
Posting to Reddit once and leaving — communities resent it; high ban risk.
Too many emojis / badges in the README — lowers credibility.
Launching an English project to Chinese communities first — wrong order, wasted shot.

FAQ

How long does it realistically take to reach 10K stars?

AFFiNE hit 10K in 43 days from public launch with this sequence (README readiness → 3-niche seeding → Show HN → 48-hour star push → sustained content). Generic launches without structure typically take 6–18 months for the same milestone.

How do I get on GitHub Trending?

Coordinate a 48-hour star push from warm contacts + community alongside a Show HN or Reddit post. The algorithm rewards star velocity, not absolute count — 150–300 stars in 48 hours usually lands a niche-language list.

Which license should I pick?

Choose deliberately — MIT maximizes adoption, Apache-2 adds patent protection, AGPL protects against closed-source forks but scares some enterprises. Decide based on whether you plan to monetize a hosted version.

Who built this?

Iris Wei (生姜) — former cofounder/COO of AFFiNE (60K+ GitHub stars), who led its organic 0 → 60K growth and advised 150+ dev-tool startups.

Related playbooks

Product Hunt Launch Playbook — Win #1 of the Day→ SEO & GEO Dual-Engine Playbook→ B2B SaaS Growth — PLG vs SLG to $10M ARR→ Browse all 40+ playbooks→