Manjaro 2.0 Synopsis This document covers the organizational, technical, management, and other changes we (the Manjaro Team, et al) like to see applied to the Manjaro Project. The goal of this document is to serve as a point of discussion, and ultimately, once a consensus on its contents and written goals has been reached, as a guide for the organizational restructuring of the Manjaro Project. Motivation The Manjaro Project has been declining over the past decade. It managed to sustain a sizabl...
They aren’t stupid to abandon the brand and community just like that and start from nothing. The team plans to start a nonprofit that will work alongside and not under the current Manjaro company. They do say that if Manjaro GmbH & Co. KG declines, or the feel that they are dragging their heels (which they have done) they will start a strike. They are doing this rn. If that fails then they will just move to the next stage which is to leave and/or fork the project.
That said, we have seen successful forks like this lately. CoMaps is a good example.
Manjaro itself is basically a fork of Arch, I thought. I’m not sure what its attraction is supposed to be, but I’ll take your word for it. I similarly don’t understand the attraction of Ubuntu over Debian.