<?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: me shih</title>
    <description>The latest articles on DEV Community by me shih (@me_shih_5584ee7fbfb262e19).</description>
    <link>https://dev.to/me_shih_5584ee7fbfb262e19</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%2F4252876%2Fb7efe7cf-7d4b-4190-abae-c55f87b6a24c.png</url>
      <title>DEV Community: me shih</title>
      <link>https://dev.to/me_shih_5584ee7fbfb262e19</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/me_shih_5584ee7fbfb262e19"/>
    <language>en</language>
    <item>
      <title>Five Signals That Tell You a GitHub Project Is Actually Alive</title>
      <dc:creator>me shih</dc:creator>
      <pubDate>Thu, 19 Nov 2026 04:58:51 +0000</pubDate>
      <link>https://dev.to/me_shih_5584ee7fbfb262e19/five-signals-that-tell-you-a-github-project-is-actually-alive-499n</link>
      <guid>https://dev.to/me_shih_5584ee7fbfb262e19/five-signals-that-tell-you-a-github-project-is-actually-alive-499n</guid>
      <description>&lt;p&gt;Every "best open source X" list has the same problem: half the projects are ghost ships. Last commit 2023, an issue queue of 900 unread, a README that still advertises a version two majors old. You find out after you've installed it.&lt;/p&gt;

&lt;p&gt;Here's the checklist I run now. It takes about five minutes per project and has saved me more time than any comparison article.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. &lt;code&gt;pushed_at&lt;/code&gt;, not the last release
&lt;/h2&gt;

&lt;p&gt;The release page lies. A project can cut a "v2.1.0" that's a version bump and nothing else, or ship nothing for a year while the repo is very much alive.&lt;/p&gt;

&lt;p&gt;What you want is &lt;strong&gt;the last commit to the default branch&lt;/strong&gt;. In the GitHub API that's &lt;code&gt;pushed_at&lt;/code&gt;. If it's within a couple of weeks, someone is in the code. If it's six months old, ask why before you install.&lt;/p&gt;

&lt;p&gt;Caveat: a mature project can legitimately go quiet. The distinction is &lt;em&gt;quiet with zero open PRs&lt;/em&gt; (maintainer may be gone) versus &lt;em&gt;quiet with 40 PRs merging&lt;/em&gt; (it's fine, the release cadence is just slow).&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Open issue count relative to stars
&lt;/h2&gt;

&lt;p&gt;Raw numbers are useless. The ratio tells you something.&lt;/p&gt;

&lt;p&gt;A project with 100k stars and 200 open issues is being triaged. A project with 50k stars and 3,000 open issues is drowning — or has decided not to triage. Neither is automatically bad, but you should know which one you're adopting, because it predicts how your own bug report gets handled.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. The license, actually read
&lt;/h2&gt;

&lt;p&gt;"Open source" is not a license. I check the SPDX identifier and then look at the exceptions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;MIT / Apache-2.0 / BSD&lt;/strong&gt; — boring, use it&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AGPL-3.0&lt;/strong&gt; — fine for internal use and self-hosting, a real consideration if you're exposing it as a service to others&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sustainable Use / BSL / "fair-code"&lt;/strong&gt; — not OSI open source. Internal use is usually fine; competing with it isn't&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The GitHub API returns &lt;code&gt;NOASSERTION&lt;/code&gt; for licenses it doesn't recognize. That's your cue to read the file, not to assume it's fine. n8n is the classic case here: 200k+ stars, hugely capable, and deliberately not OSI-licensed.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Multi-platform release artifacts
&lt;/h2&gt;

&lt;p&gt;Open the Releases page and count. If the latest release ships Windows &lt;code&gt;.exe&lt;/code&gt;/&lt;code&gt;.msi&lt;/code&gt;, macOS &lt;code&gt;.dmg&lt;/code&gt;, and a Linux &lt;code&gt;.AppImage&lt;/code&gt; or &lt;code&gt;.deb&lt;/code&gt;, the maintainers care about people who aren't going to build it from source. If it's source tarballs only, you're expected to have a toolchain — which is fine, just decide now whether that's a thing you want.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Star velocity, not star total
&lt;/h2&gt;

&lt;p&gt;Total stars measure how famous something got. Velocity measures whether it's still moving.&lt;/p&gt;

&lt;p&gt;This is where a "fastest growing" view beats a "most starred" view. A project at 8k stars adding 400 a day is doing something right now. A project at 200k stars adding 20 a week is coasting on history.&lt;/p&gt;

&lt;p&gt;I use &lt;a href="https://githubplay.com/rankings?board=rising" rel="noopener noreferrer"&gt;GitHubPlay's rising board&lt;/a&gt; for this, because it separates the four questions people actually ask — 24h hot, fastest growing, newly released, all-time stars — instead of collapsing them into one "popular" list. The numbers come straight from the GitHub REST API, so it's the same data as &lt;code&gt;api.github.com/repos/...&lt;/code&gt; just ranked.&lt;/p&gt;

&lt;h2&gt;
  
  
  The five-minute version
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;1. pushed_at within 2 weeks?          → alive
2. open issues / stars &amp;lt; 5%?          → triaged
3. SPDX is MIT/Apache/BSD/AGPL?       → safe to adopt
4. latest release has my platform?    → install-able
5. star velocity positive?            → not coasting
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Four out of five is usually enough. All five failing means you found a tutorial, not a tool.&lt;/p&gt;

&lt;h2&gt;
  
  
  One more thing I learned the hard way
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Check who's behind it.&lt;/strong&gt; A single-maintainer project with 80k stars is a bus-factor problem, not a quality problem — but you should know. Look at the contributor graph, the org, and whether there's a company funding it. That tells you what happens when the maintainer gets a full-time job.&lt;/p&gt;




&lt;p&gt;The meta-point: the useful comparison isn't "which project has more features". It's "which of these will still exist in two years, and will I be able to leave it if it doesn't". Most of that answer is in five API fields.&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>github</category>
      <category>selfhosted</category>
      <category>devops</category>
    </item>
    <item>
      <title>I Stopped Paying for Notion. Here's the Spreadsheet I Used to Pick the Replacement.</title>
      <dc:creator>me shih</dc:creator>
      <pubDate>Thu, 19 Nov 2026 04:57:34 +0000</pubDate>
      <link>https://dev.to/me_shih_5584ee7fbfb262e19/i-stopped-paying-for-notion-heres-the-spreadsheet-i-used-to-pick-the-replacement-37ee</link>
      <guid>https://dev.to/me_shih_5584ee7fbfb262e19/i-stopped-paying-for-notion-heres-the-spreadsheet-i-used-to-pick-the-replacement-37ee</guid>
      <description>&lt;p&gt;Last month our team lead forwarded a Notion invoice and asked a boring question: &lt;strong&gt;which of these docs do we actually still use?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Nobody knew. That's the thing about a wiki that lives in someone else's cloud — you never quite know how much of your institutional memory is sitting there, or what happens to it the day the seat count gets cut. So I spent a weekend going through the open-source Notion alternatives, and I did it the unglamorous way: a spreadsheet, three columns, honest scores.&lt;/p&gt;

&lt;p&gt;Here's what I learned, and where you can steal the numbers.&lt;/p&gt;

&lt;h2&gt;
  
  
  The three columns that actually decided it
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. Data ownership.&lt;/strong&gt; Not "is it open source" — that's table stakes. The real question is: &lt;strong&gt;if the company behind it disappears tomorrow, can I still open my files?&lt;/strong&gt; A self-hostable server with a SQLite dump that I can read scores high. An Electron app that phones home to a proprietary sync layer scores low, no matter how pretty the UI.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Offline reality.&lt;/strong&gt; Every app says "offline support". Most mean "we cache the last page you opened". I tested by killing the network mid-edit and reopening the app cold. Apps that came back with a full tree and a working editor went up a rank. Apps that showed a spinner for 40 seconds slid down. One app displayed my pages but silently refused to save — that's worse than failing, and it cost it the trial.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. The migration cliff.&lt;/strong&gt; This is the one people skip. Ask: &lt;strong&gt;what's the escape hatch?&lt;/strong&gt; Not import from Notion (everyone does that). I mean export &lt;em&gt;out&lt;/em&gt; — to Markdown, to plain folders, to something a future tool can read. If the export produces a mangled folder tree with UUID filenames, the answer is no.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;The honest shape of this: I didn't want a better Notion. I wanted a system where the exit cost was near zero. Once you score for exit cost instead of features, the shortlist collapses fast.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  What the numbers look like
&lt;/h2&gt;

&lt;p&gt;I ended up shortlisting three, and the thing that surprised me was how different their answers were.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;AppFlowy&lt;/strong&gt; — roughly 79k stars on GitHub, AGPL-3.0. Flutter, desktop-first, and it genuinely targets the Notion mental model (databases, boards, wikis in blocks). Export to Markdown works. Weak point: sync still wants their cloud unless you're prepared to run the stack yourself.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AFFiNE&lt;/strong&gt; — MPL-2.0, the docs+whiteboard hybrid. If your notes are 60% diagrams, this is the only one that stops feeling like a compromise.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;SiYuan (思源笔记)&lt;/strong&gt; — AGPL-3.0, local-first to its bones, encrypted-by-default. Best privacy story of the three, steepest learning curve, and the least "Notion-shaped" — which for some people is the point.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;All three live on GitHub with real release pages, so you also get the boring-but-important part: &lt;strong&gt;you can see what changed last week&lt;/strong&gt;, instead of trusting a changelog page nobody maintains.&lt;/p&gt;

&lt;h2&gt;
  
  
  The part where I stopped reading blog posts
&lt;/h2&gt;

&lt;p&gt;The failure mode of this kind of research is spending two hours on listicles that were all written from the same press release. What actually helped was a page structured around the decision instead of the product — the kind that lists each replacement with its license, whether self-hosting is real or nominal, and what the migration path is.&lt;/p&gt;

&lt;p&gt;I used &lt;a href="https://githubplay.com/alternatives/notion" rel="noopener noreferrer"&gt;GitHubPlay's Notion alternatives page&lt;/a&gt; for the sweep — it indexes them with OSI licenses and self-hosting verification, and each entry links straight to the official GitHub Releases rather than a mirror, which matters when you're about to install something on a work machine. For AppFlowy specifically, the &lt;a href="https://githubplay.com/app/AppFlowy-IO/AppFlowy" rel="noopener noreferrer"&gt;canonical repo page&lt;/a&gt; has star counts and downloads synced from the GitHub API, so you're looking at live numbers instead of a screenshot from 2023.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Caveat I'd want stated if I were reading this: these numbers move daily. Treat any star count in a blog post, including this one, as a timestamp, not a fact.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  What I'd tell you to do instead of picking from this list
&lt;/h2&gt;

&lt;p&gt;Don't pick from this list. Do this:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Pick your current worst moment.&lt;/strong&gt; For us it was "someone shares a doc, the offline copy is stale, and they edit the wrong version." That's the thing to test.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Install two, not five.&lt;/strong&gt; Trial period should be measured in hours, not weeks.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Kill your network and try to work.&lt;/strong&gt; Ten minutes. That's your real answer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Export everything once, before you migrate.&lt;/strong&gt; If the export is garbage, you learned that cheaply.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Only then&lt;/strong&gt; decide whether "close enough to Notion" even matters to you. Turns out, for us, it didn't.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;We ended up keeping a self-hosted instance and a Markdown folder that gets committed to a private repo every night. Boring architecture, near-zero exit cost. The invoice at the top of this post is now a cron job that costs nothing.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;If you're doing this comparison yourself, the &lt;a href="https://githubplay.com/alternatives" rel="noopener noreferrer"&gt;alternatives index&lt;/a&gt; groups them by the SaaS tool you're leaving, which is a faster way in than searching "open source Notion alternative" and drowning in SEO farming.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>productivity</category>
      <category>selfhosted</category>
      <category>notion</category>
    </item>
  </channel>
</rss>
