Live data from Hacker News

MinIO is now in maintenance-mode

github.com

271–280 of 338 posts

Re: MinIO is now in maintenance-mode

#271

Minio is more or less feature complete for most use cases. Actually the last big update of minio removed features (the UI). I am using minio for 5 years and haven't messed with it or used any new thingie for the last 5 years (i.e since I installed it); I only update to new versions. So if the minio maintainers (or anybody that forks the project and wants to work it) can fix any security issues that may occur I don't…

> So if the minio maintainers (or anybody that forks the project and wants to work it) can fix any security issues that may occur I don't see any problems with using it. The concerning language for me is this part that was added: > Critical security fixes may be evaluated on a case-by-case basis It seems to imply that any fixes _may_ be merged in, but there's no guarantees.

Yes this is concerning for me too. Hopefully if they don't fix/merge security issues somebody will fork and maintain it. It shouldn't be too much work. I'd even do it myself if I was experienced in golang.

Re: MinIO is now in maintenance-mode

#272
post #254

Earlier quoted context omitted.

MinIO doesn't seem to have had a CLA though?

MinIO had a de facto CLA. MinIO required contributors to license their code to the project maintainers (only) under Apache 2. Not as bad as copyright assignment, but still asymmetric (they can relicense for commercial use, but you only get AGPL). https://github.com/minio/minio/blob/master/.github/PULL_REQU...

Isn't that standard protective boilerplate so that they cant get rugpulled themselves on a contribution, 2 years later? I thought the ASF had something similar.

Re: MinIO is now in maintenance-mode

#273
post #254

Earlier quoted context omitted.

MinIO doesn't seem to have had a CLA though?

MinIO had a de facto CLA. MinIO required contributors to license their code to the project maintainers (only) under Apache 2. Not as bad as copyright assignment, but still asymmetric (they can relicense for commercial use, but you only get AGPL). https://github.com/minio/minio/blob/master/.github/PULL_REQU...

This wording was added in the template in August 2023. What's the licensing situation for community contributions before then?

Re: MinIO is now in maintenance-mode

#274
post #132

There is https://github.com/seaweedfs/seaweedfs I haver not used it but will be likely a good minio alternative for people who want to run a server and don't use minio just as s3 client.

I'm looking at deploying SeaWeedFS but the problem is cloud block storage costs. I need 3-4TB and Vultr costs $62.50/mo for 2.5TB. DigitalOcean $300/mo for 3TB. AWS using legacy magnetic EBS storage $150/mo... GCP persistent disk standard $120/mo. Any alternatives besides racking own servers? *EDIT* Did a little ChatGPT and it recommended tiny t4g.micro then use EBS of type cold HDD (sc1). Not gonna be fast, but for…

I'm confused why you would want to turn an expensive thing (cloud block storage) into a cheaper thing (cloud object storage) with worse durability in a way that is more effort to run?

I'm not saying it's wrong since I don't know what it's for, I'm just wondering what the use-case could be.

Re: MinIO is now in maintenance-mode

#275

Earlier quoted context omitted.

The _only_ reason to require a CLA is because you expect to change the license in the future. RustFS has rug-pull written all over it.

Or to offer it under a commercial licence in parallel.

That doesn't require full copyright assignment, though, right?

Re: MinIO is now in maintenance-mode

#276
post #178

Earlier quoted context omitted.

They have a CLA that assigns copyright to them: https://github.com/rustfs/rustfs/blob/5b0a3a07645364d998e3f5... So, arguably worse than MinIO.

Without a valid CLA and a strong core team, you often end up with fragmentation or legal deadlock. Even the ASF isn't a silver bullet—projects without strong leadership die there all the time. The CLA exists to prevent that friction.

Then it's not the CLA that ensures project survivability. It's the strong core team you mentioned.

Re: MinIO is now in maintenance-mode

#277
post #178

Earlier quoted context omitted.

They have a CLA that assigns copyright to them: https://github.com/rustfs/rustfs/blob/5b0a3a07645364d998e3f5... So, arguably worse than MinIO.

How would you run a project like this? People come and go. People do a one-time contribution and then you never hear from them again. People work on a project for years and then just go silent. Honestly, credit where credit is due, but how is a project like this supposed to manage this?

What do you mean by 'manage?' In your mind, what are you planning to do in the future that you need my full copyright as a change owner?

Re: MinIO is now in maintenance-mode

#278
post #132

There is https://github.com/seaweedfs/seaweedfs I haver not used it but will be likely a good minio alternative for people who want to run a server and don't use minio just as s3 client.

SeaweedFS has been our choice as a replacement for both local development and usage in our semi-ephemeral testing k8s cluster (both for its S3 interface). The switch went very smooth.

I can't really say anything about advanced features or operational stability though.

Re: MinIO is now in maintenance-mode

#279

Earlier quoted context omitted.

I'm looking at deploying SeaWeedFS but the problem is cloud block storage costs. I need 3-4TB and Vultr costs $62.50/mo for 2.5TB. DigitalOcean $300/mo for 3TB. AWS using legacy magnetic EBS storage $150/mo... GCP persistent disk standard $120/mo. Any alternatives besides racking own servers? *EDIT* Did a little ChatGPT and it recommended tiny t4g.micro then use EBS of type cold HDD (sc1). Not gonna be fast, but for…

I'm confused why you would want to turn an expensive thing (cloud block storage) into a cheaper thing (cloud object storage) with worse durability in a way that is more effort to run? I'm not saying it's wrong since I don't know what it's for, I'm just wondering what the use-case could be.

I've quickly come to this conclusion. Essentially looking for offsite backup of my NAS and currently paying around $15-$20/mo to Backblaze. I thought I might be able to roll my own object store for cheaper but that was idiotic. :-)

Re: MinIO is now in maintenance-mode

#280

Earlier quoted context omitted.

I'm confused why you would want to turn an expensive thing (cloud block storage) into a cheaper thing (cloud object storage) with worse durability in a way that is more effort to run? I'm not saying it's wrong since I don't know what it's for, I'm just wondering what the use-case could be.

I've quickly come to this conclusion. Essentially looking for offsite backup of my NAS and currently paying around $15-$20/mo to Backblaze. I thought I might be able to roll my own object store for cheaper but that was idiotic. :-)

Totally fair. There are some situations where you can "undercut" cloud native object storage on a per TB basis (e.g. you have a big dedi at Hetzner with 50TB or 100TB of mirrored disk) but you pay a cost in operational overhead and durability vs managed object store. It's really hard to make the economics work at $20 price point, if you get up to a few $100 or more then there are some situations where it can make sense.

For backup to a dedi you don't really need to bother running the object store though.

Post reply on HN