Earde — A shared home for open-source communities

Log inExplore EardeConnect a project

◈ The community platform for open source<br>A shared home for open-source communities.<br>Live chat, searchable forums, and canonical discussions shared across related project communities.<br>Open web · no account required<br>Public discussions are indexed by search engines and readable without an account.

Connect a projectExplore Earde

NetworkLive chatShared thread

What Earde does today

01<br>Build a community around your GitHub repo.<br>Verify a repository you maintain through GitHub, choose how the project should belong on Earde, and publish a real community home around it.

Verify repoChoose homeCommunity ready

02<br>Share a discussion with a connected project community.<br>An existing discussion can be shared with a connected project community. Its moderators decide whether to accept it, and where it belongs.

RequestReview

03<br>Create a shared discussion from the start.<br>Choose a connected project community while creating a thread. Once accepted there, both communities participate in the same canonical discussion and comment tree.

Create sharedShared thread

How Earde compares<br>CapabilityDiscordDiscourseZulipEardeLive chatYesYesYesYesSearchable forumsNoYesPartialYesGitHub-backedNoNoNoYesCommunity connectionsNoNoNoYesShared threadsNoNoNoYesMobile appYesYesYesIncomingVoice / videoYesNoNoIncoming

Connected communities<br>Codebases have relationships.Their communities should too.<br>Open-source projects depend on one another, but their communities still live as isolated spaces. Earde gives related project communities explicit relationships without merging their identity, moderation, or governance.

PLANNEDNot built yet.<br>Turn a settled discussion into a GitHub issue.<br>The maintainer decides every time, and the issue keeps a link back to the discussion it came from.<br>Also plannedBug reportFeature requestDocumentation draft

/c/dream / § questions / thread<br>Canonical · shared with /c/ocaml<br>How should cancellation be handled in Lwt applications?<br>14 comments · accepted answer from u/raphael-proust<br>Create GitHub issue

aantron/dream · Issues<br>OpenClarify cancellation semantics for Lwt handlers#412<br>Handlers that own a resource should wrap the body in Lwt.finalize and re-raise Lwt.Canceled after cleanup.<br>↩ earde.org/c/dream/questions/lwt-cancellation

Build a community around your GitHub repo.<br>Live chat, searchable forums, and canonical discussions shared across related project communities.<br>Connect a projectExplore Earde

Earde uses privacy-conscious analytics to understand how this page is used and improve it. Nothing is collected unless you accept.<br>ACCEPTREFUSE