A solo developer's protest fork of GNOME over UI simplification died within months. It demonstrated that declaring a fork of a major desktop environment without a team or resources is a recipe for failure.
GNOME is a massive desktop environment comprising hundreds of libraries, applications, and system components. Forking it requires maintaining compatibility with GTK, GLib, D-Bus integrations, and countless upstream dependencies. A single developer cannot realistically maintain even a fraction of this stack.
In 2004, Ali Akcaagac — a long-time GNOME contributor and former GNOME Foundation member — grew increasingly frustrated with GNOME's controversial direction toward UI simplification. The GNOME team had been systematically removing user-facing options and configuration knobs in favor of a 'less is more' philosophy, which infuriated power users and some developers who felt their workflow was being degraded.
Akcaagac submitted a patch to restore some of the removed options, but it was rejected by the GNOME maintainers. Rather than accept the decision, he announced Project GoneME — a fork of the entire GNOME desktop environment. The announcement generated significant press coverage on Slashdot, OSnews, and Linux.com, and Akcaagac reported receiving enough supportive emails in a single week to feel justified in the endeavor.
But enthusiasm in an inbox does not translate to code commits. GoneME was essentially a one-person operation attempting to fork and maintain one of the largest open-source desktop environments in existence. The project never produced a usable release, never attracted a development team, and quietly vanished within months of its announcement.
GoneME became a cautionary tale frequently cited in discussions about open-source governance. It is easy to declare a fork — the barrier to entry is literally a git command — but maintaining one requires sustained effort, community, and resources that a single frustrated developer simply cannot provide.
The irony is that Akcaagac's complaints about GNOME's direction were widely shared. Years later, GNOME 3's radical redesign would trigger the MATE and Cinnamon forks, which succeeded precisely because they had teams of committed developers and the backing of distributions like Linux Mint.
Ali Akcaagac announces Project GoneME as a fork of GNOME
Story covered on Slashdot and OSnews, generating significant discussion
Akcaagac receives supportive emails but no developer commitments
Project goes silent with no releases produced
GoneME's impact was purely cultural — it became shorthand for 'angry fork that goes nowhere.' The underlying complaint about GNOME's simplification philosophy was valid and would later fuel successful forks (MATE, Cinnamon), but GoneME itself proved that being right about the problem doesn't mean you can execute the solution alone.