Live data from Hacker News

MinIO repository is no longer maintained

github.com

371–380 of 397 posts

Re: MinIO repository is no longer maintained

#371
post #221

Earlier quoted context omitted.

If that is the case why did minio start with the open source version? If there were only downsides? Sounds like stupid business plan

Where did I say there were only downsides? There are definitely upsides to this business model, I'm just refuting the idea that because there are for profit motives the downsides go away. I hate when people mistreat the people that provide services to them: doesn't matter if it's a volunteer, underpaid waitress or well paid computer programmer. The mistreatment doesn't become "ok" because the person being mistreated…

I doubt that minio pulled the open source version because they were mistreated. Really yeah there are some projects where this is a problem, but it’s mostly because the project only has a single maintainer.

People are angry about minio , but that’s because of their rugpull.

Re: MinIO repository is no longer maintained

#372
By the way, I’ve been switching to RustFS as my S3 mock server, and it works like a charm.

They maintain the Docker image, so it works great in a k8s environment, for both local and remote development.

Big thanks to MinIO for providing this option for so many years. I genuinely wish them the best.

Re: MinIO repository is no longer maintained

#373

Earlier quoted context omitted.

Have you heard of LocalStack’s AWS emulator? [1] It’s runnable within a docker container and has a high fidelity S3 service. Disclosure, I’m a SWE at LocalStack. [1] https://github.com/localstack/localstack

I like(d) LocalStack fine, but you've got the same kind of problem that Minio has. > As a result of this shift, we cannot commit to releasing regular updates to the Community edition of LocalStack for AWS. https://blog.localstack.cloud/the-road-ahead-for-localstack/

That’s fair. There’s still a free tier that you can use.

https://blog.localstack.cloud/the-road-ahead-for-localstack/...

But IMO, LocalStack community’s S3 service is pretty stable, so I’m doubtful there’ll be much parity drift in the short to medium term.

Re: MinIO repository is no longer maintained

#374

Earlier quoted context omitted.

I'm running Firefox 145.0.2 on amd64. It seems like the issue may be that I have WebGL disabled. The console includes messages like "Failed to create WebGL context: WebGL creation failed: * AllowWebgl2:false restricts context creation on this system." Oh well, guess I can't use rustfs :}

I just disabled webgl on my firefox and it worked fine. Your problems could be caused by a whiny fan. Here is the source https://github.com/rustfs/rustfs

I like the way multiple people feel the need to defend a buggy website with their anecdotal n=1 evidence.

It’s not difficult to make a website that works for everyone.

Re: MinIO repository is no longer maintained

#375

Earlier quoted context omitted.

Lol, maybe you should fund the RustFS team yourself or sponsor a top-tier legal team for them. If you can help them rewrite their CLAs and guarantee they'll never face any IP risks down the road, then sure, you're 100% right.

Interesting that all your comments are shilling for RustFS

Fair point on the frequency of my comments, but there’s a nuance to the CLA discussion. Even with Apache 2.0, many major projects (like those under the CNCF or Apache Foundation) require a CLA to ensure the project has the legal right to distribute the code indefinitely.

My focus on the CLA is about building a solid foundation for RustFS so it doesn't face the licensing "re-branding" drama we've seen with other storage projects recently. It’s about long-term stability for the community, not just a marketing ploy.

Re: MinIO repository is no longer maintained

#376

Earlier quoted context omitted.

Lol, maybe you should fund the RustFS team yourself or sponsor a top-tier legal team for them. If you can help them rewrite their CLAs and guarantee they'll never face any IP risks down the road, then sure, you're 100% right.

And again - what IP risk does a CLA solve, that a DCO wouldn't? Like, IANAL so I certainly could be missing something, but I'd like to hear what it might be.

I’m also maintaining an open-source project and have spent significant time drafting our CLA, so I completely understand the concerns surrounding them.

While DCO is excellent for tracking provenance, we opted for a CLA primarily to address explicit patent grants and sublicensing rights—areas where a standard DCO often lacks the comprehensive legal coverage that a formal agreement provides.

It’s a common and sustainable practice in the industry to keep the core code open-source while developing enterprise features. Without a solid CLA in place, a project faces massive legal hurdles later on—whether that’s for future commercialization or even the eventual donation of the project to an open-source foundation like the CNCF or Apache Foundation. We're just trying to ensure long-term legal clarity for everyone involved.

Re: MinIO repository is no longer maintained

#377
post #143

Earlier quoted context omitted.

They're not saying they violated the license, they're saying they're assholes. It may not be illegal to say you'll do something for free and then not do it, but it's assholish, especially if you said it to gain customers.

They gave code for free, under open source, but you call them assholes if they do not release more code for free. So who is the asshole here? You or them?

Nestle started a charity to give free baby formula to mothers in African villages. Once they all stopped producing milk, they stopped the charity and made the formula so expensive it was barely affordable.

Re: MinIO repository is no longer maintained

#378

Earlier quoted context omitted.

I meant that you can't span single cluster over high latency link, unlike for example garagefs

Ceph has synchronous replication, writes have to be acked by all replicas before the client gets an ack. Fundamentally, the latency of ceph is at least the latency between the OSDs. This is a tradeoff ceph makes for strong consistency.

I know. We run it for near a decade now. I mentioned it because a lot of uses for minio are pretty small.

I had 2 servers at home running their builtin site replication and it was super easy setup that would take far more of both hardware and work to replicate to ceph so while ceph might be theoretically fitting feature list, realisticially it isn't an option.

Re: MinIO repository is no longer maintained

#379

Earlier quoted context omitted.

> Although many people criticize RustFS, suggesting its CLA might be "bait," I don't think such a requirement is excessive for open source software, as it helps mitigate their own legal risks. What legal risks does it help mitigate?

RustFS has rug-pull written all over it. You can bookmark this comment for the future. 100% guaranteed it will happen. Only question is when.

I’m Elvin from the RustFS team in the U.S. Thanks for pointing out the issues with our initial CLA. We realized the original wording was overreaching and created a lot of distrust about the project's future.

We’ve officially updated the CLA to a standard License Grant model. Under these new terms, you retain full ownership of your contributions, and only grant us a non-exclusive license to use them. You can check the updated CLA here: https://github.com/rustfs/rustfs/blob/main/CLA.md.

More importantly, the RustFS team is officially pledging to keep our core repository permanently open-source. We are committed to an open-core engine for the long term, not a "bait and switch."

Re: MinIO repository is no longer maintained

#380

Earlier quoted context omitted.

RustFS has rug-pull written all over it. You can bookmark this comment for the future. 100% guaranteed it will happen. Only question is when.

I’m Elvin from the RustFS team in the U.S. Thanks for pointing out the issues with our initial CLA. We realized the original wording was overreaching and created a lot of distrust about the project's future. We’ve officially updated the CLA to a standard License Grant model. Under these new terms, you retain full ownership of your contributions, and only grant us a non-exclusive license to use them. You can check the…

It is better, but FYI for context:

  Subject to the terms and conditions of this Agreement, You hereby grant to RustFS and to recipients of software distributed by RustFS a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works under any license, including proprietary or commercial licenses and open-source licenses, at RustFS's sole discretion.
Post reply on HN