<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Ashish Sharma</title>
    <description>The latest articles on DEV Community by Ashish Sharma (@sarmaasis).</description>
    <link>https://dev.to/sarmaasis</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4164921%2F2ca2bd2a-28cd-4753-961a-bb19d71f3ffa.jpg</url>
      <title>DEV Community: Ashish Sharma</title>
      <link>https://dev.to/sarmaasis</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sarmaasis"/>
    <language>en</language>
    <item>
      <title>I got tired of “top starred” open-source lists, so I built PickOpenSource</title>
      <dc:creator>Ashish Sharma</dc:creator>
      <pubDate>Mon, 05 Oct 2026 22:10:08 +0000</pubDate>
      <link>https://dev.to/sarmaasis/i-got-tired-of-top-starred-open-source-lists-so-i-built-pickopensource-3o8o</link>
      <guid>https://dev.to/sarmaasis/i-got-tired-of-top-starred-open-source-lists-so-i-built-pickopensource-3o8o</guid>
      <description>&lt;p&gt;I use open source software all the time, but it’s a constant struggle to find the right project.&lt;/p&gt;

&lt;p&gt;My usual process goes something like:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Search ‘open source alternative to X’&lt;/li&gt;
&lt;li&gt;Check round up posts&lt;/li&gt;
&lt;li&gt;Inspect GitHub stars&lt;/li&gt;
&lt;li&gt;Pick one&lt;/li&gt;
&lt;li&gt;Discover later that the license is weird, or that it’s a pain to self-host or that it’s abandoned&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;This happened to me over and over again.&lt;/p&gt;

&lt;p&gt;I realized the problem was a simple misassumption:&lt;/p&gt;

&lt;p&gt;GitHub stars don’t always reflect what I actually need in a project.&lt;/p&gt;

&lt;p&gt;So I built PickOpenSource.&lt;/p&gt;

&lt;p&gt;What I wanted in an open source directory&lt;/p&gt;

&lt;p&gt;When evaluating projects, I usually have decision points around:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What problem does this solve?&lt;/li&gt;
&lt;li&gt;What is the license?&lt;/li&gt;
&lt;li&gt;Can it be self-hosted?&lt;/li&gt;
&lt;li&gt;Is there a managed version?&lt;/li&gt;
&lt;li&gt;Is the repository maintained?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Usually these things are more important to me than the number of stars, so that’s what PickOpenSource focuses on.&lt;/p&gt;

&lt;p&gt;Browse by the job you need to get done&lt;/p&gt;

&lt;p&gt;The site is organized around categories like:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Analytics&lt;/li&gt;
&lt;li&gt;Authentication&lt;/li&gt;
&lt;li&gt;CMS&lt;/li&gt;
&lt;li&gt;CRM&lt;/li&gt;
&lt;li&gt;Databases&lt;/li&gt;
&lt;li&gt;Developer tools&lt;/li&gt;
&lt;li&gt;Customer support&lt;/li&gt;
&lt;li&gt;DevOps&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You pick a category, then compare projects within that category.&lt;/p&gt;

&lt;p&gt;The idea is that you start from the job that needs to get done, rather than the existing projects.&lt;/p&gt;

&lt;p&gt;The things that I care about&lt;/p&gt;

&lt;p&gt;In general I want to highlight the things that are deal-breakers or that slow down adoption:&lt;/p&gt;

&lt;p&gt;License&lt;/p&gt;

&lt;p&gt;MIT, Apache, AGPL, and custom licenses can all be deal-breakers, depending on what you’re building.&lt;/p&gt;

&lt;p&gt;I’m not a lawyer, but I think this information should be easy to find for any given project.&lt;/p&gt;

&lt;p&gt;Hosting&lt;/p&gt;

&lt;p&gt;This is a tricky one - I think people sometimes use the term ‘open source’ to mean ‘can I self-host this?’.&lt;/p&gt;

&lt;p&gt;Other times it’s a managed product that just has an open source repository.&lt;/p&gt;

&lt;p&gt;Both are totally valid, but I want to highlight that difference.&lt;/p&gt;

&lt;p&gt;Repository activity&lt;/p&gt;

&lt;p&gt;A high number of stars doesn’t mean much if the project isn’t actively maintained.&lt;/p&gt;

&lt;p&gt;The site tries to pull this information in as well, using GitHub’s API (as of roughly every 24 hours).&lt;/p&gt;

&lt;p&gt;Alternatives pages&lt;/p&gt;

&lt;p&gt;I’ve also got pages for specific queries like:&lt;/p&gt;

&lt;p&gt;open-source Google Analytics alternatives&lt;/p&gt;

&lt;p&gt;or similar products to other SaaS companies. These tend to be more helpful than general ‘best open source tools’ roundups, in my opinion.&lt;/p&gt;

&lt;p&gt;Compare pages&lt;/p&gt;

&lt;p&gt;If you narrow your options down to two, you can compare them - for example:&lt;/p&gt;

&lt;p&gt;Umami vs Plausible&lt;/p&gt;

&lt;p&gt;I think it’s helpful to be able to see the differences between two similar projects in one place.&lt;/p&gt;

&lt;p&gt;What we’ve got so far&lt;/p&gt;

&lt;p&gt;The site has:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;200+ curated projects&lt;/li&gt;
&lt;li&gt;Category pages&lt;/li&gt;
&lt;li&gt;Alternatives pages&lt;/li&gt;
&lt;li&gt;Compare pages&lt;/li&gt;
&lt;li&gt;Repository activity&lt;/li&gt;
&lt;li&gt;A small newsletter for new items&lt;/li&gt;
&lt;li&gt;Sponsored placement slots&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I think it’s still pretty early, and I’d rather spend time curating and improving information about the projects we’ve got rather than importing thousands of repositories just to have a bigger list.&lt;/p&gt;

&lt;p&gt;How sponsorship works&lt;/p&gt;

&lt;p&gt;The site has sponsorship slots, but I want to make sure that there’s a clear distinction between projects that pay to be listed, and projects that get there through curation.&lt;/p&gt;

&lt;p&gt;Sponsored projects are called out as such, and don’t affect the general discovery experience.&lt;/p&gt;

&lt;p&gt;This is important to me, because I feel like that’s the whole point of a tool like this - to make it easy to make better technical decisions. If somebody pays for a sponsored slot, that should be clear.&lt;/p&gt;

&lt;p&gt;What I want to improve&lt;/p&gt;

&lt;p&gt;I think the biggest area of improvement right now is decision guidance.&lt;/p&gt;

&lt;p&gt;For example, rather than having:&lt;/p&gt;

&lt;p&gt;Tool A vs Tool B&lt;/p&gt;

&lt;p&gt;I’d rather have something like:&lt;/p&gt;

&lt;p&gt;Pick this one if you want the easiest self-hosted setup&lt;/p&gt;

&lt;p&gt;or&lt;/p&gt;

&lt;p&gt;Pick the other one if you want managed hosting and don’t care about customization.&lt;/p&gt;

&lt;p&gt;I’m interested in reducing generic comparison copy and adding more of those specific, actionable decision points.&lt;/p&gt;

&lt;p&gt;Feedback&lt;/p&gt;

&lt;p&gt;If you’re interested in using the site, I’d love to hear:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;What categories would you like to see?&lt;/li&gt;
&lt;li&gt;What information are you looking for when considering open source tools?&lt;/li&gt;
&lt;li&gt;Did I get any of the license info wrong? Any hosting info?&lt;/li&gt;
&lt;li&gt;What SaaS alternatives pages would you like to see?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I think concrete criticism is more valuable than vague praise at this point.&lt;/p&gt;

&lt;p&gt;Try the site&lt;/p&gt;

&lt;p&gt;&lt;a href="https://pickopensource.site" rel="noopener noreferrer"&gt;https://pickopensource.site&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you maintain an open source project that should be listed, you can submit it here as well.&lt;/p&gt;

&lt;p&gt;I built this thing because I needed it, and I’m happy to say that I’ve already avoided switching to a tool that was probably the right choice but with a terrible, difficult-to-maintain open source implementation.&lt;/p&gt;

&lt;p&gt;If this helps somebody else avoid doing the same, that’s a win in my book.&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>webdev</category>
      <category>saas</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
