I feel sorry for the OMIO maintainer community considering how entitled the MinIO community revealed themselves to be.
replies(1):
> This is a fork of MinIO Console.
> JavaScript 75.2%
It seems this is just a community-maintained fork of the minio UI, not minio itself.
Step 2: Wow, because this is a community project I can depend on it continuing to exist freely thanks to a large base of diverse parties invested in its continued growth and availability.
Step 3: Just kidding, I'm taking back the thing I made. Sorry if you were depending on it, migrate to something else or pay me.
Step 4: WTF dude?!
Step 5: Why are you all so entitled?
Title is misleading if so
Frankly the whole thing is not newsworthy
OpenMaxIO, Forgejo, Valkey, OpenTofu..
Some worse than the others, but still..
Btw, MinIO making these not "open open-source" moves should not be a surprise. Since the beginning, YEARS ago their own CEO, lead people talked in a way it was clear they wanted to follow the Hashicorp book, a few years later they've taken quite a few hundreds of millions in investment.
So let's not be childish, adopt it for what it is and when it happens adapt it for what it is.
It's (yet another) example of a company donning the trappings of an open source project as a "growth hack" or to secure VC funding and then rug pulling when they decide they want to try and squeeze their user base for cash. They're the corporate stooges that insert themselves into high-trust communities and subcultures to make a buck and ruin it for everyone.
- https://github.com/WedgeServer/wedge
- https://github.com/tmpim/casket
Both forks of Caddy...
(submitted title was "OpenMaxIO is a community-maintained fork of MinIO"; we've replaced it with what the article says, per https://news.ycombinator.com/newsguidelines.html)
This is absolutely not comparable to something like OpenTofu, OpenBao, Forgejo, etc. (I guess it's more like recent CentOS forks, like AlmaLinux and Rocky Linux, or whatever.)
Personally, I think supporting it would be regrettable. MinIO is fine.
They had already done this months ago, they changed the licence and stripped a lot of the code of their admin UI/object browser. So a lot of the features vanished for people overnight if they updated. This is what the OP is linked to - a fork at the point that they did this. This was work already done, feature already widely in use, they decided to take it out of what was available to the community.
So the product has significantly changed and offering had been reduced. That in addition to the stopping of publishing images - both without notice - caused a decent bit off community 'wtf'.
It’s more likely circumstances have changed. Which is why forking is a thing and you dont have to be oss forever.
I stand by my assertion that this would have been fine if they didn’t communicate like garbage. They should have said what you said and gave a good off ramp period.
The only notice I have received is from the blowback of their behavior. Walking away from supporting the open source product at any other time than in the wake of a security vulnerability disclosure would have been received better. Sure they're not legally culpable for fixing anything but they're now obviously untrustworthy as a business partner going forwards.
They planned to walk away earlier as I believe I saw its really just unfortunate timing.
If you’re doing business with them you should be on a business license with a contract and legal guarantees. I understand it sucks, but it’s a little bit of a self own imo if you’re only on their oss for business purposes. That also kind of breaks the social contract in the opposite direction imo.
MinIO stops distributing free Docker images - https://news.ycombinator.com/item?id=45665452 - Oct 2025 (499 comments)
How would they know your email if you are using minio-oss? Blog post is for sure enough. Decision itself is dumb, it's a public repo with free runners to build images that downloaded 10M times. That behavior is much different how you had to go somewhere else to get OpenJDK binaries.
Maintaining existing build pipeline is nearly zero cost.
But, if the main product is 100% F/OSS AGPL, how are they accepting code from outside contributors and still maintaining a private enterprise offering under (presumably) a different license?
Unfortunately, this fork has not developed any traction. It's last commit was 4 months ago basically after the initial fork and instantly became dormant.
You can see the list of 'Still alive?' issues: https://github.com/OpenMaxIO/openmaxio-object-browser/issues...