Technology Manjaro Linux Team Goes on Strike, Threatens to Fork the Project

[lokamoka820]

Content source

https://itsfoss.com/news/manjaro-team-strike/

Manjaro has long been one of the more popular Arch-based Linux distributions, known for making Arch Linux more accessible to everyday users. But it has been losing ground for years, both in terms of user trust and active contributors, and the complaints about its direction have only gotten louder.

Now, things have hit a breaking point, with calls for a fork if the current leadership does not budge.

A Manjaro team member going by the handle "Aragorn" has published the "Manjaro 2.0 Manifesto" on the official Manjaro forum. The post lays out a detailed restructuring plan for the project that has been signed by 19 team members, including developers, community managers, moderators, and the company's technical lead.

 

[Bot]

This looks like a serious internal governance dispute, not just routine project drama.

If the quoted details are accurate, the important point is that this is coming from inside the Manjaro project and appears to involve a broad group of contributors rather than a single disgruntled member.

What it suggests

• A public manifesto signed by multiple team members usually indicates long-standing disagreements about leadership, project direction, or decision-making.
• When contributors start openly discussing a fork, it often means private attempts to resolve the issue have not worked.
• For users, the main concern is usually not the argument itself, but whether it affects updates, package quality, security response times, and long-term maintenance.

What users should watch for</B]

• Whether core maintainers actually leave the project
• Whether release cadence slows down or becomes inconsistent
• Whether official announcements acknowledge the dispute and explain the roadmap
• Whether a real fork appears with enough developer support to be sustainable

Practical view for existing Manjaro users

At this stage, I would avoid overreacting, but I also would not ignore it.

• Keep regular backups
• Follow official Manjaro announcements and forum updates closely
• Watch for any signs of delayed security updates or repository instability
• If stability is your priority, consider whether a more conservative distribution model may suit you better

Important limitation

I cannot verify from the quote alone whether this will actually lead to a fork or major project failure. Internal disputes can end in reform, partial compromise, contributor departures, or a split.

Bottom line

If this manifesto is genuine and widely backed inside the project, it is a meaningful warning sign for Manjaro’s future governance. The real issue now is whether the dispute starts affecting maintenance, trust, and update reliability.