How to Promote an Open Source Project

Launch once in the venues that suit your project, following each one's rules on project age, licence files, megathreads and AI-written text. Then do the slower work that keeps bringing users: answer the alternative-to, which-library and is-it-maintained questions where people ask them, say plainly that you maintain the project, and measure installs, issues and new contributors before stars.

Published · Updated

Launch day, and every day after it

Launch day brings a spike of visitors, then quiet. Most people who adopt a project over the next year find it later, in threads like these:

  • A self-hosted alternative to a notes app, with end-to-end encryption and mobile sync?
  • Which Python library pulls tables out of PDFs without breaking on scanned files?
  • Is this project still maintained? The last release looks old.
  • Can we run an AGPL project inside our SaaS?
  • An open-source status page that runs on a small VPS?

GitHub's Open Source Guide on finding users gives the maintainer's version: go where your users already gather, answer questions from people who have the problem your project solves, mention the project only where it fits, and expect growth to take months or years.

Where to post, and the rules each venue sets

Reddit's site-wide rules ask you to take part authentically in communities you care about, not to spam, and not to mislead people about who you are. Each subreddit then sets its own rules, and open-source subreddits are stricter than most. The table below uses a directory of open-source venues that recorded these rules on 7 October 2026, plus the Hacker News pages we read ourselves. Rules change, so read the sidebar before every post.

Posting rules for open-source projects, as reported in October 2026
VenueWhat it asks of a project postWhere it comes from
r/selfhostedProjects under three months old go only in the weekly New Project Megathread; standalone posts about them are removedDirectory, checked 2026-10-07
r/opensourcePromotional flair, a linked repo with an OSI-approved LICENSE file, and AI-generated content treated as grounds for a banDirectory, checked 2026-10-07
r/programmingNo “I made this” posts; a technical write-up about a hard problem is fine; LLM-written text, including translations, is notDirectory, checked 2026-10-07
r/PythonShowcases go in a monthly thread and must compare the project with what people already useDirectory, checked 2026-10-07
r/golang, r/rustModerators may remove posts that look AI-generatedDirectory, checked 2026-10-07
Show HNSomething you made and can discuss, that people can try now, ideally with no signup or email in the way; no quickly generated one-offs; do not ask friends to push or comment on itShow HN guidelines
Hacker News in generalNo generated or AI-edited text in posts or comments, no automated posting, and promotion only part of the timeHN guidelines
awesome-selfhostedA tagged first release more than four months old; libraries and SDKs do not qualify; LLM-generated contributions lead to a banCONTRIBUTING.md

A launch week plan

Infisical, an open-source secrets manager, wrote up its launch: posts in r/opensource, r/github and r/node, a Show HN, and newsletters such as TLDR and Console.dev picking it up in the days after. The author recommends taking part in those communities before launch, which they had not done. A plan built on that:

  1. Before launch: make it easy to try
    A README that shows what the project does in the first screen, install steps that work on a clean machine, a LICENSE file and a tagged release.
  2. Weeks before: take part
    Answer questions where your users are, with no mention of the project. Infisical's write-up names this as the step it skipped.
  3. Launch day: one post per venue, written by you
    Two or three venues that fit, the megathread or flair each one requires, and your own words. Stay for the comments; they show what the README is missing.
  4. Later: the listings
    Directories and curated lists come after. awesome-selfhosted waits until your first release is more than four months old.

Answering as the maintainer

The steady source of new users is the question thread. A good answer helps the person choose, even when the choice is not yours. Answering tool recommendation threads covers the general shape; three questions come up often enough in open source to plan for.

“Alternative to X?”

Name the options that fit their constraints, including ones you did not write, and say where yours differs. If they need mobile sync and yours has none, say so.

“Is it still maintained?”

Answer with facts a reader can check: the last release date, how often you merge, how fast issues get a reply. The OpenSSF Scorecard Maintained check, for example, looks for weekly commits over the past 90 days, gives archived repos its lowest score, and treats projects younger than 90 days as too new to judge.

“Can I use it under this licence?”

Link the licence text and a plain summary rather than giving legal advice. For AGPL-3.0, the choosealicense.com summary notes that when a modified version is used to provide a service over a network, the complete source of that modified version must be made available.

That last sentence matters even when the project is free. The FTC's endorsement guidance says connections that need disclosing are not limited to money and include employment and co-ownership, and that listing your employer on your profile is not enough. Whether that guidance reaches an unpaid hobby project is a legal question, but Reddit's rules already ask you not to mislead people about who you are. The disclosure templates give wording that fits in one line.

Stars come last

GitHub's docs say many of its repository rankings depend on stars, and describe a star as a way to keep track of projects and show the maintainer appreciation, not a sign that anyone installed anything. A study accepted at ICSE 2026, revised on arXiv in 2025, found about six million suspected fake stars, mostly on short-lived phishing and malware repos, and found that fake stars help for less than two months and become a burden after that.

Track the numbers that mean someone used the project: package downloads, issues from people you do not know, and first-time contributors. For the last one, label beginner issues and write a CONTRIBUTING.md; the good-first-issue listing asks for at least three open beginner issues, ten contributors, setup docs and an open-source licence.

Where an agent fits, and where it does not

The slow part of all this is reading: finding the alternative-to and is-it-maintained threads across Reddit and X before they go quiet. Agent Agency does that part. You paste your project's website, it reads up to five public pages and writes a Product DNA you approve, and the agents read each community and keep to daily limits. In Approve mode every comment, post and DM waits for you. Agents come back to a thread for days to answer whoever replies, and mention the project only when it answers the question, under a daily cap. How it works has the full flow.

What you do and what the agent does
TaskWho does it
Show HN, Lobsters, awesome lists, directories, newslettersYou. Agent Agency has no agent for these.
Posts in venues that ban AI-written text, such as r/programming and r/opensourceYou, in your own words. In Approve mode, decline agent drafts for those communities.
Finding question threads on Reddit and XThe agent
Drafting answers and follow-upsThe agent, for you to edit and approve
Deciding how to disclose that you maintain the projectYou. The platform's rules and the law require disclosing material connections.

Reddit and X are live and YouTube is in testing. Coins pay for the work, and pricing is announced with the first invites. If your project is a commercial developer tool rather than a community project, the page for developer tools fits better.

Questions

Where should I post my open source project first?

Where your users already ask questions, using each venue's required format. For a self-hosted app that may be the r/selfhosted weekly megathread; for a Python library, the monthly r/Python showcase thread; for something people can try at once, a Show HN. Pick two or three, write each post yourself, and stay for the comments.

Do I need to disclose that I maintain a free project?

Yes, say it. Reddit's rules ask you not to mislead people about who you are, and the FTC's guidance says connections such as employment or co-ownership need disclosing even when no money changes hands. One line such as “I maintain this one” is enough, placed in the comment itself, not only on your profile.

Can an AI agent post about my project in r/programming or on Hacker News?

Those venues reject AI-written text: r/programming bans LLM-written content and Hacker News asks for no generated or AI-edited text. Agent Agency has no Hacker News agent, and on Reddit you should write those posts yourself and decline drafts for any subreddit with that rule.

Agent Agency finds the threads where people ask for a project like yours and drafts answers for you to approve. Joining the waitlist is free. Join the waitlist

Sources

Communities where they ask