Manjaro Linux Faces Major Shake-Up as Team Demands Leadership Reform

Manjaro Linux, one of the most popular Arch-based distributions, is experiencing a major internal crisis that could reshape its future. The project, known for making Arch Linux more accessible to everyday users, is now at a crossroads as key team members demand fundamental changes to its leadership structure.

Breaking Point Reached After Years of Decline

A Manjaro team member known as “Aragorn” has published a detailed manifesto titled “Manjaro 2.0 Manifesto” on the official Manjaro forum. This document has been signed by 19 team members, including developers, community managers, moderators, and the company’s technical lead. The manifesto represents a coordinated effort to address what the team describes as a decade-long decline in the project’s health and direction.

The manifesto opens with a stark assessment: the Manjaro Project has been declining over the past decade, losing trust and contributors while repeating the same mistakes without ever addressing them. One specific example cited is the repeated failure to keep TLS certificates current—a problem that volunteers had already built tooling to fix, only to be ignored by leadership.

Core Issues Identified

The manifesto directly accuses Philip Müller, the project lead, of running Manjaro as his personal venture rather than a community effort. According to Aragorn, Müller has maintained tight control over access to both the codebase and infrastructure, creating a bottleneck that has stifled innovation and community involvement.

The document states: “The priorities of the Project leadership do not align with those of the developers and community. The current leadership’s goal is to turn Manjaro into a successful business, and thus far, these attempts have mostly failed.”

The financial situation adds another layer of complexity. The manifesto claims that Manjaro GmbH & Co KG, the company behind the project, has not been funneling any of its funds back into development and has not pursued outside funding either. This lack of investment has reportedly contributed to the project’s stagnation.

Proposed Restructuring Plan

The team’s solution is comprehensive: spin off the Manjaro Project from Manjaro GmbH & Co KG and restructure it as a registered nonprofit association under German law (e.V.). This new structure would distribute ownership equally among members, implement transparent voting for major decisions, and assign “arbiter” roles to experienced contributors for specific domains.

Under the proposal, the nonprofit would gain full use of the Manjaro trademark through 2029, with the company retaining rights to use it as long as the two entities don’t conflict. After this initial period, the manifesto suggests the company should be willing to hand over full trademark ownership to the nonprofit for just €1.

Critical infrastructure assets including GitHub organizations, the self-hosted GitLab instance, forums, CDN, and the manjaro.org domain would all transfer to the nonprofit entity.

Three-Stage Escalation Plan

The manifesto outlines a clear escalation path if demands aren’t met. The team has established three stages (0-2): waiting for a reply, striking and going public, and finally forking or leaving the project entirely. Within Stage 1, there are three phases controlling the document’s visibility.

The team has already progressed through these phases, moving the manifesto to the public Announcements section of the forum and archiving it on archive.org. This represents a significant escalation, as it makes the internal conflict visible to the entire community.

Clarification from Team Members

Dennis ten Hoove, another Manjaro team member, has clarified that the initiative’s goal is not to remove people from the project but to change the leadership structure and foster a healthier, community-driven approach to development.

Leadership Response and Stalemate

Philip Müller eventually broke his silence, stating he is fine with an association being formed but wants no part in setting one up himself. He emphasized that any transfer of assets would need to happen on the company’s terms and warned that public statements damaging to the business could have legal consequences.

The protesting team’s response was measured. Aragorn pointed out that the manifesto already allows the company to continue using infrastructure for as long as needed to move operations elsewhere. Roman Gilg, who signed the manifesto despite being the company’s CTO, directly asked Philip if he had any specific objections to the list of assets outlined in the document. Philip went silent again.

After days without response, Aragorn declared that Philip was stalling and announced the team was skipping Phase 2 and moving straight to Phase 3—the current state of affairs.

Community Reaction and What’s Next

An active community discussion thread with over 200 replies has emerged, providing a space for broader community input on the situation. Longtime Manjaro contributor Stefano Capitani has weighed in, acknowledging past conflicts but expressing confidence that the project will emerge stronger.

The situation remains fluid, with the potential for a fork looming if negotiations break down completely. The manifesto’s authors have made clear their commitment to the project’s success, even if that means creating a separate entity to achieve their vision.

This crisis represents more than just an internal dispute—it highlights the challenges faced by open-source projects as they grow and the tension between community-driven development and commercial interests. The outcome could set precedents for how similar projects handle governance and leadership transitions in the future.

The Manjaro community now watches closely as this drama unfolds, with the future of one of Linux’s most popular distributions hanging in the balance. Whether through reform or fork, significant changes appear inevitable for a project that has served as many users’ gateway to the Arch Linux ecosystem.

Tags: Manjaro Linux, Arch Linux, Linux distribution, open source, community governance, software development, Philip Müller, fork, nonprofit, e.V., German law, manifesto, leadership crisis, Manjaro GmbH, trademark, infrastructure, TLS certificates, community-driven development

Viral Phrases:

• “Manjaro 2.0 Manifesto”
• “Breaking point reached”
• “Fork if leadership doesn’t budge”
• “Community-driven project”
• “Stalling and silence”
• “Three-stage escalation plan”
• “Legal consequences warning”
• “Gateway to Arch Linux”
• “Open-source governance crisis”
• “Trademark for €1”
• “Decade-long decline”
• “Personal venture accusations”
• “Infrastructure takeover”
• “Community discussion explosion”
• “Fork looming”
• “Leadership reform demanded”
• “Nonprofit restructuring”
• “Asset transfer battle”
• “Community confidence expressed”
• “Future of Manjaro uncertain”

,