They need to cast out the person who can't renew the ssl certificate.
Technology
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
Who renews certificates these days? You automate that now, especially with 47 day certs coming.
That's the level of incompetency that needs to be booted
My renewals have been running in a crontab for five years without any hiccups. The fact they can't do that is simply lazy.
This is why I'm going to argue for pure Arch or Artix. Ultimately, what a lot of these distros bring to the table is artwork. But they bite off a lot more than artwork when doing so. And in time they can start to suck at that administration.
It's not very hard to set up your system with a vanilla DE and adjust it into something good. You don't need to get fancy. And to the extent someone else's art work can be good and accelerate getting to a nice system, there are other ways to distribute that.
You should want your distro to be 95% administration and 5% art because in the long run that's whats going to keep your system stable and avoid future headaches. But some artists are overly ambitious and envision creating an entire version of an operating system, including the parts they aren't passionate about. And some people buy in on this premise and install these projects. ...instead of just releasing dot files.
For it to go well requires that both the leadership and the contributors are passionate about all of the parts and passionate about them forever. Not very likely. If you want a distro that is administered well, get a distro where administration is all they do, and then get your artwork as a separate selection.
Now you can get your art from artists who put 95% of their effort into art. And your package stability by people who put 95% of their effort into package stability.
Everyone has romantic feelings toward a system that is integrated. But what they should realize is that integrated and modular are opposites. And modular is what they should want, with effective roll separation.
If they fork Majaro that is good. If when they fork it they scope down to just distribute a dot file set, and maybe create their own easy installer for Arch that isn't a seperate whole distro, that is better.
Honestly the damage is done. Manjaro has been an instant no from me dog for a long time. The name carries a negative connotation. Trust has eroded.
What happened?
The trust. It eroded.
I mean, I think they were looking for a little more detail that that.
Over a hundred thousand years the ocean of distrust has eroded the cliffs of trust in a non-insignificant manner.
Plenty of things, but the most obvious being the two separate instances they had issues with renewing their certs.
It's more than that. Broken updates. Failed hardware ventures. The project has been shambling along for a long time.
and the certs lapsed again after volunteers built tooling to Prevent That
but somebody never set up the cron job to run it
Failing to renew TLS certificates on time multiple times is enough to never touch it again, but there's also been a lot of other problems with Manjaro.
When I used Manjaro, it never made it more than 6 weeks before something would catastrophically break and I'd have to roll back using snapshots.
As others suggest, why stay attached to Manjaro at all? Instead of forking, what about expending that energy on a rising distro without such reputational damage?
CachyOS is very close “in spirit” if they want to develop modified/custom packages, but there are plenty Arch downstream distros with less toxic communities.
They could even fork some other project and make the changes they like. It’d be a saner base than Manjaro at this point.
You are assuming that the cachy devs want the help of folks who have not demonstrated competence in their own project or want to do stuff how manjaro does
EndeavorOS too, which is even closer to "vanilla" Arch than CachyOS.
The fact that CachyOS more or less successfully replaced Manjaro's purpose I guess is evidence of Manjaro's issues.
I forgot but I think Bazzite had similar complaints (due to its use of silverblue) in which case it was just more straightforward to use Fedora or OpenSUSE if you don't want to work with the read only root system.
Downstream distros need to bring additional value to the table to be worth using, otherwise there's really no need if you can make a package group that accomplishes the same thing in one go.
Good for them! A second TLS problem after what happened last time is unacceptable. I hope the 'mutiny' succeeds.
Already thought about migrating to EndeavorOS. I hope they can manage to keep the whole thing going.
I made that switch a year ago and it has been great, manjaro cause me alot of little issues I dint realize we're manjaro specific.
awh comon I just installed it for the first time, what's wrong with Manjaro?
I wouldn't necessarily say it's bad, but I don't use it because:
- The project's had a history of failing at really basic administrative tasks like keeping their ssl certificate up to date
- I'm unconvinced they actually do the testing that justifies the delays and not just using arch. This is because security patches sometimes also get delayed and issues have gotten past the delay
- They've accidentally DDoSed the aur multiple times by shipping broken versions of pamac when fixed versions were available
- I've seen complaints about leadership and how they handle finances, though I haven't really looked into this
It’s not so much that the distro is bad, but the leadership of the project, according to a lot of the community working on it, is very unresponsive, bad at administration, doesn’t make decisions that need to be made in a timely manner and not really doing their job. The community basically wants to cut them out and move on.
Don't worry, it's just the open-source version of the market correcting. There's no stock, no venture capital. If the group putting in time and effort to help maintain something doesn't like how the project is being run, they take a copy and start over with a new name. It's happened countless times on OS, it'll happen countless more. Often, the existing leadership is burned out, some of the more active members move on, and those left through attrition lack the skills to keep it going. The forks generally move forward faster and cleaner with more active people. Other than needing to change distros, it's pretty much a win.
I haven’t used Arch for quite a while but doesn’t it come with an install script now which makes the installation more automated? That should enable a lot more people to install Arch instead of e.g. Manjaro I suppose. I’m not an expert on Manjaro but are there any meaningful positives to pick Manjaro over Arch?
Just fork already. EndeavourOS exists, an awesome distro, so this threat is a triviality.
Aragorn writes that Philip Müller (the project lead) has been running Manjaro as his own personal venture rather than a community effort, keeping a tight hold on access to both the codebase and the infrastructure.
These weasels never care about the actual thing that is being built, its just a way to make money for them.
Hope they kick that Philip guy out and get back to making this a passion project.
The core members with passion for the actual thing should restart under a new name.
Did I just find next distro to try? :) Kudos to them anyway (yay, that's the kind of news I want to hear)
Doesn't look like it. But the project will now go to the to-be-founded non-profit association.
Philm actually replied around the time of your comment, sharing his disdain that this plan was set in motion, while as company owner he has no one to talk to legally, since the association has not been founded yet. He's supportive of the move, and technically he's right. The association should've already been founded, to be fair.
I hope this means Manjaro will thrive!
I started using Manjaro long before all this crap started going down, and I've been holding on hoping this all gets sorted because I hate distto hopping.
But sadly I don't think its going to happen. I've got a new PSU coming to fix a burnt out one that has left my desktop turned off and unupdated for two months. Might be time for an install of something new rather than updating afterwards.
Switching distros was not on my agenda. 🙃
Me neither. The more I dwell on it, the grumpier I'm getting. Distro hopping is a young man's sport. I've got work to do.
Thankfully, I learned the hard way a long time ago that my files are almost entirely on a secondary drive and my home folders are all simply symlinks to folders there, so I won't lose any data since that drive won't be wiped. But it's just such a pain in the butt to set up everything the way I like it.
A significant portion of the Manjaro team has signed a manifesto demanding the project split from its parent company and restructure as a non-profit.
Sourav Rudra 18 Mar 2026
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.
Is there any weight behind this?
The manifesto opens by stating that the Manjaro Project has been declining over the past decade, losing trust and contributors while repeating the same mistakes without ever addressing them.
One example cited is the repeated failure to keep TLS certificates current, something volunteers had reportedly already built tooling to fix, only to be ignored.
From there, it goes after the core issue directly. Aragorn writes that Philip Müller (the project lead) has been running Manjaro as his own personal venture rather than a community effort, keeping a tight hold on access to both the codebase and the infrastructure.
Aragorn goes on to say that:
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 money situation makes it worse. The manifesto says the company, Manjaro GmbH & Co KG, has not been funneling any of its funds back into the project and has not pursued outside funding either. **What the team wants is a clean separation, where the Manjaro Project is spun off from Manjaro GmbH & Co. KG and restructured as a registered nonprofit association under German law (e.V.).
The new structure would distribute ownership equally among members, use transparent voting for major decisions, and assign "arbiter" roles to experienced contributors for specific domains.
Under the proposal, the nonprofit would get full use of the Manjaro trademark through 2029. The company keeps the right to use it too, as long as the two don't step on each other's toes. After that initial period, the manifesto nudges the company to declare that it is willing to hand over full trademark ownership to the nonprofit for €1.
Key assets like the GitHub organizations, the self-hosted GitLab instance, forum, CDN, and the manjaro.org domain would all move over to the non-profit as well. **The team has also laid out what would happen if they were ignored. The "Our Resolve" section of the manifesto says that there are three stages (from 0-2): waiting for a reply, striking and going public, and finally forking or leaving. Within Stage 1, there are three phases that control how public the document gets.
They skipped Phase 2 and jumped straight to Phase 3 a few days ago, moving the manifesto to the public Announcements section of the forum and archiving the thread on archive.org. If things don't improve, then a forum lockdown is on the table. **Don't think that this is some kind of witch hunt. One of the Manjaro team members, Dennis ten Hoove, has clarified that the goal of this initiative is not to kick people off the project but to change the leadership and help foster Manjaro as a healthy community-driven project.
Expect a bumpy transition
Philip did break his silence on the matter, saying that he is fine with an association being formed but wants no part in setting one up himself. He also made clear that handing over any assets would need to happen on the company's terms and closed with a warning that public statements damaging to either himself or the business could have legal consequences.
The protesting team's response was measured, where Aragorn pushed back, pointing out that the manifesto already lets the company continue using the infrastructure for as long as it needs to move its operations elsewhere.
Roman Gilg, who signed the manifesto despite being the company's CTO, put a direct question to Philip, asking whether he had any specific objection to the list of assets outlined in the document. Philip went quiet again.
After days of silence on that question, Aragorn declared that Philip was stalling and announced the team was skipping Phase 2 and moving straight to Phase 3 (where things stand as of now).
What can you do?
There's an active community discussion thread with over 200 replies, started specifically to accommodate talks surrounding the manifesto. If you have thoughts on what's going wrong with the Manjaro project and what could be done better, you can head over and weigh in.
One of the Manjaro old timers, Stefano Capitani, has recently posted there, sharing his view of the situation:
I have to apologize to all of you. It seems I’ve missed some of the events here. I believe, without fear of contradiction, that I, along with @guinux , @oberon , and of course @philm, am one of the “old timers” still active, if not as much as before, but still active in Manjaro.
I have to be honest, I feel like I’m having flashbacks because we’ve already had these discussions or “storms” in the past. We’ve always come out stronger, and we’ll come out stronger this time too.
PS: You need to be logged in to the Manjaro forum to view user profiles.
The manifesto opens by stating that the Manjaro Project has been declining over the past decade, losing trust and contributors while repeating the same mistakes without ever addressing them.
Philip did break his silence on the matter, saying that he is fine with an association being formed but wants no part in setting one up himself. He also made clear that handing over any assets would need to happen on the company's terms and closed with a warning that public statements damaging to either himself or the business could have legal consequences.