An open-source launch week is not a single announcement. It is a coordinated sequence: make the positioning understandable in seconds, publish one reusable source story, reach the communities where relevant users already gather, respond to feedback, and measure adoption beyond GitHub stars. The launch only works if the product and team can absorb the attention.
Open-Source Launch Week: From Zero to 6,000 Stars
At 1:47 a.m. on August 3, 2022, I was sitting beside an engineer and asking him to change the font size on a website we had assembled the day before.
We had decided to open-source AFFiNE on July 24. That gave us one week to prepare everything. When we finally clicked Public, none of us knew whether anyone would care.
The repository received about 200 stars on day one, 800 on day two, and another thousand on day three. By the end of the first week, it had reached roughly 6,000 stars.
That is a useful story, but it is not a universal launch formula. It is a first-party account from one product, one team, and one moment in the open-source ecosystem. The part worth reusing is not the number. It is the sequence of decisions behind it.
The launch starts with a story, not a public repository
Before AFFiNE launched, I studied AppFlowy. I went back to its launch week and looked at the directories, articles, README, positioning, and community communication that had helped people understand it.
The lesson was simple: a stranger needs an anchor. “Open-source alternative to a familiar product” may feel less sophisticated than a page full of adjectives, but it gives the reader a fast way to understand the category and the difference.
Our early positioning connected AFFiNE to Notion and Miro. It was not perfect, but it was legible. A launch message should answer three questions in seconds:
- What is this?
- Who is it for?
- Why would they try it now?
Four jobs for the first 24 hours
The first day had four operating jobs.
Make the value proposition repeatable. Everyone on the team should be able to explain the same product promise without inventing a new version.
Publish one source story. A strong launch article becomes the material that communities, newsletters, creators, and future comparison pages can reference. It should explain the problem, product, trade-offs, and next step—not just announce that a repository exists.
Cover researched channels. We prepared directories and communities by studying where comparable projects had already appeared. Channel fit matters more than posting everywhere. Platform norms also change, so tactics that worked in 2022 should be rechecked before reuse.
Reach relevant people directly. Early outreach works best when the recipient already cares about the category and the message is honest about why the project may be relevant. It is not a license for bulk spam.
| Launch job | Deliverable | What to verify |
|---|---|---|
| Positioning | One-sentence category and difference | A new reader can repeat it |
| Product proof | README, screenshots, quick start | The product can be tried |
| Source story | One substantive launch article | Others can cite or summarize it |
| Distribution | Prioritized channel list | Each channel has audience fit |
| Community | Response owner and escalation path | Feedback does not disappear |
Launch week is seven days, not one
The most common failure I see is treating launch day as the finish line. The team posts, celebrates, replies for a few hours, and then returns to normal work.
The following six days are where product learning accumulates. Questions need answers. Issues need triage. Repeated confusion should change the README or onboarding. Useful users should feel that someone is listening.
During AFFiNE’s early period, some of the most valuable contributors were people who spent real time documenting bugs or writing detailed feedback. That relationship was not created by a star count. It came from taking their effort seriously.
Attention is not the same as adoption
A successful launch can still fail commercially. Stars can increase while activation remains weak. A community can grow while the team has no plan for support, hosting, enterprise needs, or paid services.
Before launch, decide what open source is supposed to achieve: product learning, adoption, contribution, recruiting, ecosystem reach, commercial demand, or something else. Then instrument the next step.
The first hundred users are especially valuable as evidence, not merely as a growth chart. The companion guide on finding and learning from your first 100 users explains how to preserve that signal.
The first week can create momentum. It cannot substitute for a product people can use, a team that responds, or a business model that can absorb the attention. If you need to design the launch sequence and the path after it, review Gingiris advisory services.
Frequently asked questions
What matters most in the first week of an open-source launch?
Clear positioning, a useful README, a source story others can reference, relevant distribution, fast community response, and a plan for converting attention into product learning.
Should an open-source launch optimize for GitHub stars?
Stars can show attention, but they do not equal active users, contributors, or revenue. Define the business and product outcome before choosing launch metrics.
Is there a fixed formula for GitHub Trending?
No public, stable formula can be treated as a guarantee. Short-term attention may matter, but teams should not present experience-based patterns as an official algorithm.
Which metrics should an open-source team track after launch?
Track traffic sources, repository attention, installs or sign-ups, issues, useful feedback, contributors, community response, and qualified commercial conversations separately.