discourse/discourse

Prefer upstream unless you must support an old Heroku-based installation. This fork is a legacy deployment snapshot with a few Heroku-centric operational tweaks, not a modern alternative to Discourse.

Adopt this fork only if you specifically want its customized baseline and can own ongoing maintenance. If you want current Discourse capabilities, this looks too stale and divergent to be a low-risk starting point.

Choose this fork only if you specifically want the g0v-specific Traditional Chinese production setup and are comfortable inheriting a very stale, highly divergent Discourse branch. For most adopters, upstream is the safer choice.

Choose this fork if you want a custom, production-tuned Discourse for Edgeryders-style operations and can accept upgrade debt. Choose upstream if you want maximum compatibility, fewer surprises, and easier long-term maintenance.

Prefer this fork only if you specifically need its PingCAP-tailored behavior and are willing to own the maintenance burden. If you want current Discourse features, security fixes, and lower operational risk, upstream is the safer choice.

Prefer this fork only if you need the DAO-specific 2016 customization set and are prepared to maintain a large legacy codebase. For most adopters, upstream Discourse is the better choice because this fork is stale, far behind, and likely missing modern platform capabilities.

Prefer this fork only if you need a legacy 2016 Discourse snapshot with a few targeted fixes and are willing to own the long-term maintenance. For most adopters, upstream Discourse is the safer and more capable choice.

Prefer upstream unless you specifically need this legacy state. This fork looks useful only when preserving an old deployment or a very narrow historical customization matters more than features, security, and maintenance.

Prefer this fork only if you specifically need its question-centric UX and allow-list workflow. If you want a broadly supported Discourse deployment with current fixes and easier upgrades, upstream is the safer choice.

Choose this fork only if CircleCI-specific legacy workflow compatibility matters more than staying current with upstream. For most adopters, upstream is the safer default because this fork is stale, materially behind, and likely expensive to upgrade.

Choose this only if its specific multisite/hostname behavior is the point and you are prepared to maintain a long-lived legacy fork. For most adopters, upstream Discourse is the better base because this fork is stale and materially behind.

Prefer this fork only if you need a legacy Discourse snapshot and are willing to own the maintenance debt. For most adopters, current upstream is the better choice because this fork is stale and materially divergent.

Prefer this fork only if you need the exact legacy 2018 behavior and can accept owning a long-term maintenance burden. For most adopters, upstream Discourse is the safer choice because this fork is far behind and highly divergent.

Prefer this fork only if you specifically need an old, customized Discourse base and are prepared to own maintenance. For most adopters, upstream is the safer choice because this fork is stale and substantially behind.

Choose this fork only if you specifically need an old Discourse snapshot. For almost everyone else, upstream is the better choice because it is far more complete, current, and maintainable.

Choose this fork only if Cloud66 deployment support is the main requirement; otherwise upstream Discourse is the safer choice because it is far newer, actively maintained, and much less divergent.

Prefer this fork only if you specifically need the old 2013 codebase and its early fixes. For any new deployment or active community site, current upstream Discourse is the better choice.

Prefer this fork only if you need its specific custom behavior and can maintain a substantial upstream gap. If you want a stable, current Discourse base with low upgrade friction, upstream is the better choice.

Prefer this fork only if you need its specific legacy fixes or compatibility behavior and are prepared to own a dated codebase; otherwise upstream is the safer choice.