Gingiris Opensource

🇺🇸 Open-Source Marketing & GitHub Stars Growth System — Decision framework for each growth stage. Pre-launch readiness → Show HN / Reddit / Product Hunt launch → 6-month growth loop. README rules, KOL outreach, dev-content matrix (dev.to / Zenn), anti-star-farming. Built from taking AFFiNE 0 → 60K stars. 🇨🇳 开源营销与 GitHub Star 增长系统 — 每个增长阶段的决策框架。Pre-launch 就绪 → Show HN / Reddit / Product Hunt 发布 → 6 个月增长循环。README 规则、KOL 合作、开发者内容矩阵（dev.to / Zenn）、防刷 star。提炼自 AFFiNE 0 → 60K star 实战。 🇯🇵 オープンソースマーケティング＆GitHub スター成長システム — 各成長段階の意思決定フレームワーク。Pre-launch → Show HN / Reddit / Product Hunt → 6ヶ月成長ループ。READMEルール、KOL連携、開発者コンテンツマトリックス。 🇰🇷 오픈소스 마케팅 & GitHub 스타 성장 시스템 — 각 성장 단계별 의사결정 프레임워크. 사전 출시 → Show HN / Reddit / Product Hunt → 6개월 성장 루프. README 규칙, KOL 아웃리치, 개발자 콘텐츠 매트릭스. Triggers: "open source marketing" | "GitHub stars" | "star growth" | "Show HN" | "Hacker News launch" | "OSS launch" | "developer marketing" | "Reddit launch" | "dev.to" | "open source growth" | "开源营销" | "GitHub star 增长" | "开源发布" | "Show HN 怎么发" | "开发者营销" | "オープンソース" | "오픈소스 성장"

Open-Source Marketing — GitHub Stars Growth System

🌍 Language / 语言: English | 中文

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 staged decision framework used to take AFFiNE from 0 to 60K stars.

---

English Version

The 3-stage framework

Stage 1 — Pre-launch (T-30 → T-0)

• README in English-first; the first screen must be understandable in <3 seconds.
• Demo video ≤ 60s, captioned.
• License chosen deliberately (MIT / Apache-2 / AGPL each carry traps).
• 3–5 early maintainers / contributors lined up.
• Community channel live (Discord or Telegram, English-first).

Stage 2 — Launch (T-0 → T+14)

• Product Hunt (run the dedicated launch sequence).
• Hacker News Show HN — Tuesday 9am ET, or Saturday.
• Reddit — pick 3 relevant subs (r/selfhosted, r/programming, one niche tech sub).
• Deep technical posts on dev.to / Zenn / CSDN.
• 3–5 KOLs to amplify (activity > follower count).

Stage 3 — Growth (T+14 → T+180)

• One technical blog per week.
• Turn GitHub Issues into content (user questions → FAQ → posts).
• Monthly update (mailing list + Discord).
• Localize for going global (Japan/Korea first).

Channel order that works

English > multilingual > Chinese-only. Unless your target is Chinese users, launching an English project to Chinese communities first wastes your best shot.

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.
• ❌ Treating Show HN as a one-shot — engage every comment for the full day.

What to do next

• Stage 1 done → run the Product Hunt launch sequence.
• Show HN succeeds → add SEO monitoring on "<project> github".
• Need a content engine → move to the blog-writing workflow.
• Spotted a competitor's new play → run a competitor teardown.

---

中文版

3 阶段框架

阶段 1 — Pre-launch（T-30 → T-0）

• README 英文主，首屏 <3 秒读懂。
• Demo video ≤ 60s，带字幕。
• License 选对（MIT / Apache-2 / AGPL 各有陷阱）。
• 3–5 个早鸟 maintainer / contributor。
• 社群频道就位（Discord 或 Telegram，英文为主）。

阶段 2 — Launch（T-0 → T+14）

• Product Hunt（走统一发布流程）。
• Hacker News Show HN — 周二美东 9am 或周六。
• Reddit — 选 3 个相关 sub（r/selfhosted、r/programming、细分技术 sub）。
• dev.to / Zenn / CSDN 发技术深度文。
• 找 3–5 个 KOL 转（活跃度 > follower 数）。

阶段 3 — Growth（T+14 → T+180）

• 每周 1 篇技术 blog。
• GitHub Issues → 内容素材（用户问题变 FAQ）。
• 每月 1 次 update（邮件列表 + Discord）。
• 出海本地化（日韩先）。

渠道顺序

英文 > 多语言 > 纯中文。 除非目标就是中文用户，否则把英文项目先发中文社群是浪费最好的一次机会。

反模式

• ❌ 刷 star（GitHub 很快检测，后果是搜不到）。
• ❌ Reddit 只发一次就跑（社群反感，易被 ban）。
• ❌ README 太多 emoji / badge（降低可信度）。
• ❌ 把 Show HN 当一锤子买卖（要回一整天评论）。

---

By Iris (生姜 Iris) · ex-COO @ AFFiNE (0 → 60k★) · Install: npx skills add Gingiris-1031/gingiris-opensource