11 comments

[ 2.9 ms ] story [ 25.5 ms ] thread
I feel sorry for the OMIO maintainer community considering how entitled the MinIO community revealed themselves to be.
Hey I know picking names is hard, but this is the first time I've ever been on the other end of a collision like this.
Why "open". The point here is freedom. You're going to give RMS an ulcer poor fellow.
What's up with the naming of rage forked projects?

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.

This hitting the front page made me do a web search review what's going on with MinIO, and... turns out it's still 100% F/OSS, released under the AGPLv3.

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.

I'm not entirely sure how their commercial offering works. It looks like it's a commercial fork of MinIO, but I wasn't able to find anything about assigning copyright for pull requests in their Github. (I didn't look that hard).

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?

You assume competence. Minio originally tried to argue AGPL infects client code over the network.

Just let the company fade away..

This was in response to MinIO/AIStor removing the browser-console UI from the community offering (locking it behind enterprise licensing) a few months back.

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...

That's usually what happens to these type of forks.