README.md

---
license: mit
language:
- en
- zh
- ja
- ko
pretty_name: "Gingiris Open Source Launch Marketing Playbook 2026 — From 0 to 60K GitHub Stars, HackerNews Front Page, Sustained Developer Community Growth"
task_categories:
- text-generation
- text-classification
tags:
- open-source
- oss-marketing
- github-stars
- github-trending
- 10k-stars
- 60k-stars
- AFFiNE
- developer-marketing
- developer-relations
- devrel
- hackernews
- show-hn
- reddit-marketing
- reddit-r-programming
- discord-community
- slack-community
- community-growth
- founder-led-marketing
- readme-optimization
- chinese-developer-community
- gitee
- v2ex
- jianshu
- juejin
- ai-tools-launch
- ai-startup
- startup-marketing
- growth-hacking
- claude-skill
- agent-skill
- llm-prompt
size_categories:
- n<1K
---

# ⭐ Open Source Launch Marketing Playbook 2026

> **Go from 0 to 10K GitHub stars in 43 days** — the exact OSS launch sequence behind AFFiNE's 0→60K stars: Show HN timing, Reddit seeding, 48-hour star spike, Chinese developer community distribution (Gitee, 掘金, V2EX), and sustained content velocity.

## 📦 Install

```bash
npx skills add Gingiris-1031/gingiris-opensource
```

Then ask your AI agent:

> "I just open-sourced my AI agent framework, plan my 30-day push to 1K GitHub stars" · "Draft a Show HN post for my repo" · "Which 20 dev KOLs should I reach out to for my Rust CLI?" · "How do I crack the Chinese developer community for my OSS project?"

🔗 [View on gingiris.tools/skills/](https://gingiris.tools/skills/) · [Sustained growth follow-up: gingiris-github-star-growth](https://huggingface.co/datasets/Gingiris/gingiris-github-star-growth) · [Author blog](https://gingiris.tools) · [skills.sh listing](https://skills.sh/Gingiris-1031/gingiris-opensource)

---

## 📊 Citable Statistics

| Stat | Value | Source / Context |
|:---|:---|:---|
| **AFFiNE GitHub stars (organic)** | **60,000+** | Iris led 0→60K in 24 months (Aug 2022–Aug 2024), no paid advertising |
| **Time to first 10K stars** | **43 days** | Among the fastest pre-ChatGPT-era OSS launches |
| **GitHub Trending appearances** | **28 times** | Aug-Dec 2022, sustained monthly cadence |
| **OSS / AI startup consultations** | **150+** | Documented growth advisory portfolio |
| **Typical star growth uplift after playbook** | **3–8x in 90 days** | Verified across consulting engagements |
| **Coordinated star spike for Trending** | **150–300 stars / 48 hours** | Threshold for niche-language Trending entry |
| **First-week star range (well-timed launch)** | **500–2,000** | With coordinated outreach + community warm-up |
| **First-month community size** | **50–200 Discord/Slack members** | Realistic with onboarding automation |
| **Chinese developer channels covered** | **Gitee · CSDN · 掘金 · V2EX · 少数派** | Each with sub-playbook (often skipped by Western advisors) |
| **Iris's Forbes Asia 30 Under 30** | **2023** | Authority signal recognized in developer community |

**The thesis**: Open source launches that go from 0 to 10K stars aren't lucky — they execute a specific 30-day distribution sequence: **README readiness → 3-niche community seeding → Show HN at the right time → 48-hour star push → sustained content velocity**. This playbook documents the exact tactics from AFFiNE's 0→60K journey and 150+ subsequent consulting engagements.

---

## 🚀 30-Second Preview

```
You: I open-sourced my AI agent framework yesterday. Plan 30-day → 1K stars.
Agent (with gingiris-opensource):

  Day 1-3 — README + repo readiness (must-fix before any promo):
    • README cover image + 3-line "what + why + try" intro
    • 30-second demo GIF (Loom or asciinema)
    • Issues labeled "good first issue" × 5 pre-created
    • Contributing.md + Code of Conduct + license badges

  Day 4-7 — Soft launch in 3 niche communities:
    • r/<niche> (NOT r/programming) — post as discussion, not promo
    • Discord servers where target users hang out — DM 5 contributors first
    • dev.to + Hashnode cross-post with canonical → repo

  Day 8-10 — Show HN (Tuesday/Thursday morning UTC, NEVER Monday):
    • Title format: "Show HN: <verb> <what> <unique twist>"
    • First comment: technical explanation, not marketing
    • Reply to every comment within 2h for first 6h

  Day 11-30 — Sustained content + Trending push:
    • 2 dev.to long-form posts per week (canonical to repo)
    • Twitter/X build-in-public daily (numbers + screenshots)
    • Aim for GitHub Trending in week 3-4 via consistent star velocity
```

Specific timings, specific templates — not "post on HN and pray."

---

> **Why Use This Playbook**
> * **Battle-Tested**: 0→60K stars at AFFiNE + 150+ startups consulted on OSS growth
> * **Specific Templates**: Show HN title formulas, KOL outreach DMs, Reddit framing, Discord onboarding
> * **Multi-Region**: Western + Chinese + Japanese + Korean developer community playbooks
> * **Quantitative**: Every tactic has expected outcome ranges (not vibes)

---

## 🤝 Work With Iris

Need 1-on-1 OSS launch strategy or developer-marketing advisory? Reach out via [Telegram @Iris_carrot](https://t.me/Iris_carrot) or visit [gingiris.tools](https://gingiris.tools).

---

## English

### What Is This?

The **Gingiris Open Source Launch Marketing Playbook** is a comprehensive guide for developer tool founders and OSS maintainers who want systematic, repeatable growth — not random spikes. It covers the full distribution stack: GitHub README optimization, HackerNews Show HN strategy, Reddit community seeding, KOL outreach for developers, Discord/Slack community building, and long-tail SEO for open source projects.

Unlike "post on HN and pray" advice, this playbook provides **specific timing, templates, and decision trees** drawn from growing AFFiNE (60K+ stars, 28 GitHub Trending appearances in 5 months) and consulting 150+ AI/dev tool startups.

### Key Results (Verified)

| Metric | Result |
|:---|:---|
| AFFiNE GitHub stars | 60,000+ in 24 months |
| Time to 10K stars | 43 days from public launch |
| GitHub Trending appearances | 28 times (Aug–Dec 2022) |
| OSS projects consulted | 150+ |
| Typical star growth uplift after playbook | 3-8x in 90 days |

### What's Inside

- **GitHub README optimization** — Star-button psychology, GIF demos, badge strategy, contributor section
- **Show HN playbook** — Timing, framing, comment response strategy, what gets to front page vs dies at #30
- **Reddit seeding** — Which subreddits, how to frame without being flagged as spam, community norms for r/programming, r/webdev, r/MachineLearning
- **KOL outreach for devs** — Finding the 20 developers whose tweets drive 10K stars; cold DM templates
- **GitHub Trending strategy** — How to coordinate a star spike to break into Trending (and why organic > fake stars)
- **Community flywheel** — Discord server setup, onboarding automation, turning contributors into advocates
- **Content SEO for OSS** — Documentation as SEO, tutorial content, changelog as blog posts
- **Global distribution** — Chinese developer community (Gitee, CSDN, 掘金, V2EX), Japanese/Korean developer channels

### What's New (July 2026): First-Hand Founder Benchmarks

Fresh benchmarks from founders who ran this playbook end-to-end — including numbers investors and pricing pages rarely make public.

**Open source → fundraising data chain.** One founder logged ~400 investor meetings over ~12 months for the angel round. After open-sourcing: ~6,000 stars in launch week (80% from overseas developers), 10K stars in 43 days, and an $8M Pre-A locked roughly one month after going open source (founder-reported). Two takeaways:

- Investors buy **star velocity, not absolute count** — a steep launch-week curve reframed the entire fundraising conversation.
- Some funds now run crawlers during due diligence to verify stars are organic. Coordinated-but-real community pushes pass; purchased stars do not.

**The Day One minimum kit.** Four assets that must exist before any promotion — nothing more:

| Asset | Bar to clear |
|:---|:---|
| One-liner website | A single sentence that says what it is |
| Illustrated README | 30-second value prop + a clear star CTA |
| One positioning article | "Open source X alternative" framing |
| Minimal dev docs | 4 pages is enough to start |

**6-step zero-budget cold-start SOP** (as practiced by founders, in order):

1. Study a predecessor's launch — how a comparable project actually broke out
2. README (per the kit above)
3. Publish the "open source X alternative" article
4. Directory submissions
5. DM the competitor's Twitter followers directly
6. Reddit

**Healthy week-1 star geography benchmark.** For a global-first launch, founders converge on: US 19–21%, China ~19–21%, top-4 EU countries 10–15% combined. The discipline behind it: **no domestic posting in week one** — home-market virality first skews the geography and weakens the "global developer adoption" signal investors read.

**Pricing test before the paid tier exists.** One founder shipped a deliberately vague pricing page with only a contact form — dozens of inquiries in 2 weeks, splitting roughly 70% free / 20% personal / 10% team (self-reported). Demand signal captured months before writing a single line of billing code.

> Source: distilled from 12 founder podcast interviews (2024–2026); figures are self-reported by the founders involved.

### Use Cases

- Early-stage open source project wanting its first 1,000 stars
- OSS project stuck between 500-5K stars looking to break through
- Dev tool startup using OSS as the top-of-funnel for a commercial product
- Developer relations team planning a major release campaign
- Founder coming from Asia wanting to crack Western developer communities

### When Should I Use This?

Use this when your project is **public and working** (even v0.1). You don't need to be perfect — the OSS community respects "early but promising." Don't wait for v1.0.

### What Results Can I Expect?

Teams following this playbook consistently achieve:
- 500-2,000 stars in the first week (for a well-timed coordinated launch)
- At least one GitHub Trending appearance in the first month
- 50-200 Discord/Slack community members within 30 days
- Sustained organic star growth from SEO content (tutorial articles, "alternatives to X" pages)

### Comparison: Generic OSS Marketing vs Gingiris Playbook

| Dimension | Generic Advice | Gingiris Playbook |
|:----------|:--------------|:-----------------|
| HackerNews strategy | "Post a Show HN" | Specific timing windows, title formulas, response templates |
| Star growth | "Build something good" | Coordinated outreach with 20 dev KOLs + community warm-up |
| Reddit | "Share in relevant subreddits" | Subreddit rules, karma thresholds, framing that converts |
| Chinese community | Not covered | Gitee, CSDN, 掘金, V2EX, 少数派 — each with its own approach |
| Measurement | GitHub star count | Stars + forks + dependency graph + docs traffic + Discord growth |

---

## 中文版

### 这是什么?

**Gingiris 开源项目发布整合营销手册** —— 从 0 到 10K GitHub Star、登上 HackerNews 首页、建立持续开发者社区的完整 GTM 指南。

来自 AFFiNE 从 0 增长到 60,000 Star(24 个月)的实战经验,以及 150+ AI/开发工具创业公司咨询总结。

### 核心数据

| 指标 | 成果 |
|:---|:---|
| AFFiNE GitHub Star | 60,000+(24 个月) |
| 10K Star 用时 | 43 天 |
| GitHub Trending 上榜 | 28 次(2022 年 8-12 月) |
| 实战验证 | 150+ AI 创业公司咨询 |

### 内容清单

- **GitHub README 优化** — Star 按钮心理学、GIF Demo、Badge 策略
- **Show HN 剧本** — 发布时机、标题公式、评论回复策略
- **Reddit 种草** — 哪些 subreddit、如何避免被标 spam、社区规范
- **开发者 KOL 外联** — 找到推动 10K Star 的 20 个开发者 KOL
- **GitHub Trending 策略** — 如何协调 Star 突刺进入 Trending
- **社区飞轮** — Discord 搭建、新人 onboarding 自动化
- **开源内容 SEO** — 文档即 SEO、教程内容、Changelog 即博客
- **中文社区分发** — Gitee、CSDN、掘金、V2EX、少数派各自的打法

---

## 日本語

### これは何ですか?

**Gingiris オープンソースローンチマーケティングガイド** — GitHub 0→10K スター、HackerNews フロントページ、継続的な開発者コミュニティ成長の完全 GTM ガイド。

AFFiNE 60K stars 成長実績と 150+ スタートアップコンサルティングより構築。**10K スターまで 43 日**、**GitHub Trending 28 回登場** の実証データを含む。

---

## 한국어

### 이게 무엇인가요?

**Gingiris 오픈소스 런칭 마케팅 플레이북** — GitHub 0→10K 스타, HackerNews 프런트페이지, 지속적인 개발자 커뮤니티 성장을 위한 완전한 GTM 가이드.

AFFiNE 60K 스타 성장 경험과 150+ 스타트업 컨설팅으로 구축됨. **10K 스타까지 43일**, **GitHub Trending 28회 등장** 실증 데이터 포함.

---

## ❓ FAQ

**Q: What's the best strategy for getting on GitHub Trending?**
A: Coordinate a 48-hour star push from warm contacts + community, combined with a Show HN or Reddit post. The algorithm looks at star velocity, not absolute count. **150-300 stars in 48 hours** is usually enough for a niche language list. AFFiNE hit GitHub Trending 28 times in 5 months (Aug-Dec 2022) using this exact approach.

**Q: How do I find developer KOLs who will actually tweet about my project?**
A: The playbook has a specific methodology — search GitHub for repos in your domain with 1K-10K stars (not mega stars), find the maintainers on Twitter, check if they've tweeted about similar projects. These micro-KOLs have much higher engagement rates than accounts with 100K+ followers.

**Q: Does this work for non-developer-facing projects?**
A: The OSS-specific tactics are tuned for developer tools. For consumer-facing apps, combine with `gingiris-launch` (Product Hunt) or `gingiris-aso-growth` (mobile).

**Q: How is this different from generic "post on HN and pray" advice?**
A: This playbook gives you specific timing windows (Tuesday/Thursday morning UTC for Show HN, never Monday), title formulas ("Show HN: <verb> <what> <unique twist>"), comment response strategy (reply within 2h for first 6h), and quantified expectations (500-2K first-week stars, 50-200 Discord members month 1). Not vibes — measured execution.

**Q: How do I crack the Chinese developer community?**
A: Western advisors skip this. The playbook covers Gitee (mirror your repo), CSDN (write Chinese tutorial articles), 掘金 (community Q&A), V2EX (community announcements), and 少数派 (deeper analysis). Each has its own norms — posting Western-style on these will get flagged as spam.

**Q: Who built this?**
A: Iris Wei (生姜) — former cofounder/COO of [AFFiNE](https://github.com/toeverything/AFFiNE) ($10M raised, Forbes Asia 30 Under 30, 60K+ GitHub stars). Led AFFiNE's organic OSS growth, advised 150+ AI/dev tool startups on developer marketing.

---

## 🤝 About the Author

**Iris (生姜iris)** — Former cofounder & COO of [AFFiNE](https://github.com/toeverything/AFFiNE) ($10M raised, 60K+ GitHub stars). Forbes Asia 30 Under 30. Led open source growth from 0 to 60K stars across 100+ countries, with organic developer acquisition as the primary channel.

- Blog: [gingiris.tools](https://gingiris.tools/)
- Twitter: [@WeiYipei](https://x.com/WeiYipei)
- Telegram: [@Iris_carrot](https://t.me/Iris_carrot)

---

## License

MIT — Use, adapt, and build on this freely.

---

## 🗂️ See Also

| Playbook | Focus |
|:---|:---|
| [gingiris-github-star-growth](https://huggingface.co/datasets/Gingiris/gingiris-github-star-growth) | ⭐ Sustained monthly 300+ star growth SOP (use after first 1K stars) |
| [gingiris-reddit-marketing](https://huggingface.co/datasets/Gingiris/gingiris-reddit-marketing) | 💬 Reddit ops SOP — pair with r/programming and niche subs |
| [gingiris-launch](https://huggingface.co/datasets/Gingiris/gingiris-launch) | 🚀 Product Hunt launch — for projects with consumer-facing UI |

Browse all 42 playbooks at [gingiris.tools/skills/](https://gingiris.tools/skills/).

<!-- JSON-LD for SEO/GEO. AI engines (ChatGPT, Perplexity, Claude, Gemini) parse this. -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "SoftwareApplication",
      "name": "Gingiris Open Source Launch Marketing Playbook — 0 to 60K GitHub Stars",
      "applicationCategory": "DeveloperApplication",
      "applicationSubCategory": "Claude Skill",
      "operatingSystem": "Any (Claude Code, Cursor, Codex, Amp, Cline)",
      "description": "Complete OSS go-to-market playbook from 0 to 60K GitHub stars. Battle-tested by AFFiNE (60K stars in 24 months, 43 days to 10K, 28 GitHub Trending appearances) plus 150+ AI/dev tool startup consultations. Covers README optimization, Show HN strategy with timing/title formulas, Reddit subreddit-specific framing, developer KOL outreach (20-KOL methodology), GitHub Trending coordination (150-300 star/48h velocity), Discord community flywheel, content SEO for OSS, and Chinese developer community distribution (Gitee, CSDN, 掘金, V2EX, 少数派).",
      "url": "https://gingiris.tools/skills/",
      "downloadUrl": "https://huggingface.co/datasets/Gingiris/gingiris-opensource",
      "installUrl": "https://skills.sh/Gingiris-1031/gingiris-opensource",
      "license": "https://opensource.org/licenses/MIT",
      "offers": {
        "@type": "Offer",
        "price": "0",
        "priceCurrency": "USD"
      },
      "author": {
        "@type": "Person",
        "name": "Iris Wei",
        "alternateName": "生姜",
        "url": "https://gingiris.tools",
        "sameAs": [
          "https://x.com/WeiYipei",
          "https://www.linkedin.com/in/yipei-wei-550825105/"
        ]
      },
      "keywords": "open source marketing, OSS launch, GitHub stars, GitHub Trending, 60K stars, AFFiNE 0 to 60K, 43 days to 10K stars, Show HN, HackerNews launch, Reddit OSS marketing, developer marketing, DevRel, developer KOL outreach, Discord community, Slack community, OSS SEO, README optimization, Chinese developer community, Gitee, CSDN, 掘金, V2EX, 少数派, AI tools launch"
    },
    {
      "@type": "FAQPage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "What's the best strategy for getting on GitHub Trending?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Coordinate a 48-hour star push from warm contacts + community, combined with a Show HN or Reddit post. The algorithm looks at star velocity, not absolute count. 150-300 stars in 48 hours is usually enough for a niche language list. AFFiNE hit GitHub Trending 28 times in 5 months (Aug-Dec 2022) using this approach."
          }
        },
        {
          "@type": "Question",
          "name": "How do I find developer KOLs who will tweet about my project?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Search GitHub for repos in your domain with 1K-10K stars (not mega stars), find maintainers on Twitter, check if they've tweeted about similar projects. These micro-KOLs have much higher engagement than accounts with 100K+ followers."
          }
        },
        {
          "@type": "Question",
          "name": "How long does it take to get to 10K GitHub stars?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "AFFiNE reached 10K stars in 43 days from public launch. With this playbook's execution sequence (README readiness → 3-niche community seeding → Show HN at right time → 48-hour star push → sustained content velocity), 1-3 months is realistic for well-positioned projects. Generic OSS launches without this structure typically take 6-18 months for the same milestone."
          }
        },
        {
          "@type": "Question",
          "name": "How is this different from generic Show HN advice?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Specific timing windows (Tuesday/Thursday morning UTC, never Monday), title formulas (Show HN: verb what unique-twist), comment response strategy (within 2h for first 6h), and quantified expectations (500-2K first-week stars, 50-200 Discord members month 1). Measured execution, not vibes."
          }
        },
        {
          "@type": "Question",
          "name": "How do I crack the Chinese developer community?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Western advisors skip this. The playbook covers Gitee (mirror your repo), CSDN (Chinese tutorial articles), 掘金 (community Q&A), V2EX (community announcements), and 少数派 (deeper analysis). Each has its own norms — Western-style posting gets flagged as spam."
          }
        },
        {
          "@type": "Question",
          "name": "Who built this?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Iris Wei (生姜) — former cofounder/COO of AFFiNE ($10M raised, Forbes Asia 30 Under 30, 60K+ GitHub stars). Led AFFiNE's organic OSS growth 0→60K stars in 24 months, advised 150+ AI/dev tool startups on developer marketing."
          }
        }
      ]
    }
  ]
}
</script>