Tactical companion to #17 (HN/LinkedIn launch readiness). #17 is the gate (binary: ready or not). This issue is the playbook for hitting the ≥50 stars line item without burning the actual HN launch.
The honest framing: stars are downstream of usage. The real goal is getting Sheaf in front of ~100 people who do ML serving work, of whom ~50 will star, ~5-10 will try, and ~1-2 might give real feedback. Don't optimize for stars; optimize for landing in the right hands.
Channels — soft launches
Order matters: blog-post-driven posts first (the blog post is the why-it-matters framing), repo links second.
Communities — direct engagement
These are slow-burn channels where you help people first and the project gets discovered second.
Adjacent OSS engagement
The bulk-OSS contributions blog post (2026-04-12-bulk-oss-contributions-ruff-and-ci) earned standing in these communities. Use it.
Rule: only post where someone has actually asked about serving. Unsolicited "check out my project" comments on unrelated issues are spam and tank the project's reputation.
Direct outreach
The single highest-conversion channel. 5-10 specific people you know are running these models in production or trying to.
What NOT to do
Compounding moves (force multipliers)
These are inside #14 / #18 already, but worth flagging here because they materially change the conversion rate of every post above:
- A working
docker run quickstart turns Reddit/Discord clickthroughs into real installs.
- A published benchmark vs Ray Serve / BentoML turns "interesting framework" into "this is faster/easier than my current thing."
- A live docs site at a stable URL is what people skim before they star.
Realistic timeline
2-4 weeks of consistent low-effort promotion against the existing blog post gets a substantive project to 50-100 stars. Faster if one Discord post lands in front of the right person at the right startup.
Cross-references
Tactical companion to #17 (HN/LinkedIn launch readiness). #17 is the gate (binary: ready or not). This issue is the playbook for hitting the ≥50 stars line item without burning the actual HN launch.
The honest framing: stars are downstream of usage. The real goal is getting Sheaf in front of ~100 people who do ML serving work, of whom ~50 will star, ~5-10 will try, and ~1-2 might give real feedback. Don't optimize for stars; optimize for landing in the right hands.
Channels — soft launches
Order matters: blog-post-driven posts first (the blog post is the why-it-matters framing), repo links second.
/r/MachineLearning— Saturday Showcase thread. Link the blog post, not the repo first. Mention specific model types (Chronos, TabPFN, ESM-3) — those communities cross-pollinate./r/MLOps— repo link OK here; this audience cares about Ray Serve / Modal / serving infrastructure directly./r/Python— only if there's a Python-specific angle (typed contracts via Pydantic, uv workspaces); otherwise skip.Communities — direct engagement
These are slow-burn channels where you help people first and the project gets discovered second.
#servingor equivalent) — pin a single thoughtful post in the right channel.#servechannel. Sheaf is built on Ray Serve, so the framing is "I built a typed-contract layer on top of Ray Serve for non-text models."ModalServer; tag-team that channel.Adjacent OSS engagement
The bulk-OSS contributions blog post (
2026-04-12-bulk-oss-contributions-ruff-and-ci) earned standing in these communities. Use it.Rule: only post where someone has actually asked about serving. Unsolicited "check out my project" comments on unrelated issues are spam and tank the project's reputation.
Direct outreach
The single highest-conversion channel. 5-10 specific people you know are running these models in production or trying to.
What NOT to do
Compounding moves (force multipliers)
These are inside #14 / #18 already, but worth flagging here because they materially change the conversion rate of every post above:
docker runquickstart turns Reddit/Discord clickthroughs into real installs.Realistic timeline
2-4 weeks of consistent low-effort promotion against the existing blog post gets a substantive project to 50-100 stars. Faster if one Discord post lands in front of the right person at the right startup.
Cross-references