Orviqa

Where to post open-source projects: the best communities by fit

By Bright Oparaji12 min read

The best community for your project is the one where people already have the problem it solves. Size comes second, and a long list of places to post comes nowhere.

There is no single best community for open-source projects. There is a best community for your project, and it is usually smaller and more specific than the ones that appear in lists. A focused forum where your exact problem is discussed every week will send you users. A huge general site will send you a spike of visitors who leave.

This article compares the communities maintainers most often consider: who reads them, what kind of project fits, what format works, what to check about promotion, and the mistakes that get posts ignored or removed. Then it shows how to judge fit for your own project, with worked examples.

One rule applies to everything below. Rules change and differ between sub-communities. Nothing here says a community permits promotion. Read the current rules of the specific forum, subreddit or server before you post, every time.

The communities at a glance

CommunityTypical audienceFits bestFormat that worksWhat to check about promotionCommon mistake
Hacker News (Show HN)Developers, founders, technical generalistsSomething people can try right now: tools, libraries, technical demos"Show HN" post plus a first comment from the authorThe Show HN guidelines and the site guidelines, including the request not to solicit upvotesPosting a landing page or a signup wall instead of something usable
RedditDepends entirely on the subredditProjects with a clear topic home (a language, a framework, self-hosting)A text post about the problem, with the link insideEach subreddit's own rules, flair requirements and account-age limitsPosting the same link to ten subreddits on the same day
GitHub DiscussionsPeople who already found your repositoryAny project, for questions, ideas and announcementsQ&A threads, announcements, release discussionsYour own rules, since you run itSwitching it on and never answering
MastodonDevelopers and open-source enthusiasts across many serversOpen-source tools, especially with a visual or a storyShort post with an image and relevant hashtagsYour server's rules on promotional postsPosting with no hashtags, so nobody outside your followers sees it
DEV CommunityDevelopers reading tutorials and experience postsProjects with something to teachAn article about the problem and the solution, with codeThe community guidelines and appropriate tagsPublishing a press release instead of an article
Discord and Slack communitiesMembers of a specific ecosystem or interestProjects built for that ecosystemA short post in the showcase channel, then answering questionsThe server's pinned rules and which channel allows projectsPosting a link in a general or help channel
LobstersExperienced programmers interested in technical depthLow-level tools, languages, systems work, in-depth write-upsA link with accurate tags, marked as your own workInvitation-only membership and norms against mostly self-postingJoining only to post your own project
Curated "awesome" listsPeople browsing for tools in a categoryUsable projects with documentationA one-line pull request following the list's formatEach list's contributing guide and entry criteriaIgnoring the format or adding a project that does not meet the criteria
Ecosystem newslettersSubscribers following a language or fieldNotable releases and new tools in that ecosystemA short submission, where the newsletter accepts themHow submissions are accepted, if at allSending a long pitch instead of one sentence and a link
Stack OverflowPeople with a specific, current problemProjects that genuinely answer a question being askedAn answer that solves the problem, mentioning your project where it fitsThe site's rules, which require disclosing that you made itAnswering with only a link to your project

Hacker News

Audience. A large, mostly technical readership: developers, people building companies, and generalists who like technical detail.

What fits. Show HN is for something you made that others can try. Libraries, tools, technical demos and experiments with an interesting idea behind them do well. A product that requires signing up before anyone can see it fits poorly.

Expectations. Readers are direct. Expect blunt criticism, questions about how it works, and comparisons with alternatives. Answering those well in the thread matters as much as the post itself.

Format. A title starting "Show HN:", a link to the project, and a first comment from you saying why you built it, how it works and what is unfinished. The Show HN launch guide covers the rules and the first hours in detail.

Common mistakes. Asking friends to upvote, which the site's guidelines prohibit and which is detected. Posting marketing language. Disappearing after posting.

Reddit

Audience. Whatever the subreddit is about. There are communities for nearly every language, framework, tool category and hobby, and their cultures differ widely.

What fits. Projects with an obvious home: a Rust tool in a Rust subreddit, a self-hosted app among self-hosters, a frontend library in a web development community. General programming subreddits are harder, because readers there have no shared problem.

Expectations. Many subreddits limit or ban self-promotion, require a flair or a particular day for project posts, or remove posts from new accounts. Others welcome projects that are shared as a discussion. The only way to know is to read the rules and look at what has been posted recently.

Format. A text post that explains the problem the way that community talks about it, then what you built, with the link in the body. Ask a specific question to start a conversation.

Common mistakes. Cross-posting the same text everywhere at once. Posting from an account that has never taken part in the community. Treating a removal as bad luck rather than reading the rule that caused it. Our post on posting your project without getting removed goes deeper into reading a removal.

GitHub Discussions

Audience. People who have already found your project. That makes it the least useful place for reaching new people and the most useful for keeping the ones who arrive.

What fits. Every project with users. Questions that would clutter the issue tracker, feature ideas, show-and-tell from users, and release announcements.

Expectations. That someone answers. An empty Discussions tab, or one full of unanswered questions, tells visitors the project is quiet.

Common mistakes. Turning it on and leaving it. If you cannot answer within a few days, keep questions in issues instead.

Mastodon

Audience. Spread across many independent servers, with a sizeable open-source community. Some servers, such as Fosstodon, focus on free and open-source software.

What fits. Open-source tools with something to show: a screenshot, a short recording, a release with a story.

Expectations. There is no recommendation algorithm, so posts travel through follows, boosts and hashtags. Accounts that only announce their own work tend to get little response.

Format. A short post, an image with alt text, the link, and two or three relevant hashtags.

Common mistakes. No hashtags. No image description. Posting from a new account with no history of talking about the topic.

DEV Community

Audience. Developers reading tutorials, opinion pieces and experience reports.

What fits. A project with something to teach: the problem it solves, how you approached it, what you learned.

Format. A proper article with code, linking to the project as part of the story. Use the tags readers follow for that topic.

Common mistakes. Publishing release notes or a sales page as an article.

Discord and Slack communities

Audience. Members of one ecosystem: a framework, a language, a game engine, a field.

What fits. Projects built specifically for that ecosystem. A plugin for a framework belongs in that framework's server more than anywhere else.

Expectations. Most servers have a channel for showing projects and remove them elsewhere. Members expect you to be around afterwards to answer questions.

Common mistakes. Posting in a general or help channel. Joining, posting and leaving.

Lobsters

Audience. A smaller, experienced programming community that values technical depth.

What fits. Systems programming, languages, developer tooling and detailed write-ups. Applications aimed at non-developers fit poorly.

Expectations. Membership is by invitation from an existing member, and the community discourages accounts that mostly post their own work. Read the about page before asking anyone for an invitation.

Lists, newsletters and question sites

Curated lists and newsletters work differently from forums: an editor decides. A pull request to an "awesome" list that follows its format and meets its criteria can send readers for years. Newsletters for a language or field often accept submissions; check how before sending.

Question sites such as Stack Overflow reward answering the question asked. If your project genuinely solves it, say so and disclose that you made it, as the site's rules require. An answer that is only a link to your project will be removed.

How to evaluate community fit

Before posting anywhere, answer five questions about each candidate:

  1. Do people here already have the problem? Search the community for the problem, not your project's category. If nobody has asked about it in a year, they will not care that you solved it.
  2. Can they use what you built? A library for one framework is useless to people who use another. A self-hosted app needs people who run servers.
  3. What do the rules say today? Promotion rules, flair, required days, account age, showcase channels.
  4. What did well here recently? Read a week of posts. Notice the format of the ones people engaged with.
  5. Can you stay for the conversation? A post you cannot follow up on is worse than no post.

Score each candidate honestly and post to the two or three that answer best. Then post to the next ones over the following weeks, not on the same day.

Matching projects to communities: examples

These are illustrative projects, not real ones, to show the reasoning.

A Rust command-line tool that parses large log files quickly. Strong fit: the Rust subreddit and the Rust community forum, both full of people interested in fast command-line tools, and Show HN, where a quick tool someone can install and try fits the format. Later: Lobsters, if you can get an invitation, and Mastodon. Poor fit: Product Hunt, whose audience is looking for finished products rather than command-line utilities.

A self-hosted photo library for families. Strong fit: self-hosting communities, where people actively look for replacements for hosted services, and the forum of the container platform most of them run. Later: Mastodon, and Show HN once a demo is available without installing. Poor fit: framework-specific developer chats, whose members are there to discuss code.

A form validation library for a frontend framework. Strong fit: that framework's Discord or forum showcase and its subreddit, and a DEV article showing a hard validation problem and how the library handles it. Later: the framework's newsletter and a relevant "awesome" list. Poor fit: general self-hosting or end-user communities.

A Python package for cleaning messy CSV data. Strong fit: data science and Python communities where people post messy-data questions, and answering those questions on Q&A sites, with disclosure. Later: a DEV or blog tutorial with a real dataset, and Python newsletters. Poor fit: communities focused on systems programming.

Why relevance beats reach

Posting everywhere feels productive and rarely works. Each community has its own expectations, and a post written for all of them fits none. Moderators notice the same link appearing across many places at once, and a removal in one community can make the next one more suspicious of your account.

A relevant community also gives you better feedback. Ten replies from people who have your exact problem will tell you more than a thousand visitors who glanced at the README and left. Those replies are where your next improvements, and your first real users, come from.

Checklist: choosing where to post

  • List the places where people discuss the problem your project solves
  • Remove any where people could not use what you built
  • Read the current rules of each remaining community
  • Read a week of recent posts in each, and note what did well
  • Pick two or three strong fits for launch, and schedule the rest over the following weeks
  • Write each post for its own audience
  • Plan to stay and answer questions after posting
  • Keep a note of what happened in each, including removals

Build your own shortlist

The open-source launch planner takes your project's category, audience and objective and suggests which of these communities fit, which to try later and which to skip, with draft outlines for each. If you are not sure your README will hold the people a post sends, run it through the README quality checker first. For the full sequence from audience to measurement, see the open-source launch checklist.

← All posts