Why We Forked cxx-qt, SABnzbd, OpenRazer, and tail-tray

Thu, 24 Sep 2026 08:00:00 -0500

Somewhere along the way the word fork picked up a hostile ring, as if clicking that button were the opening move in a community schism instead of the cheapest way to make a dependency do one thing differently, and the folklore costs real time, because teams that need a one-line fix will contort themselves with wrapper layers, patch scripts, and vendored tarballs rather than be seen maintaining a fork, when the fork was the honest tool for the job from the start. Four of the repos under the visorcraft organization are forks of other people’s projects, none of them are hostile, and each one has a different relationship to its upstream, which is the part worth writing down, because the interesting question was never “should you fork” but “what do you do with the fork six months later.”

Forks on VisorCraft News

Why We Forked cxx-qt, SABnzbd, OpenRazer, and tail-tray