Live data from Hacker News

MinIO is now in maintenance-mode

github.com

21–30 of 338 posts

Re: MinIO is now in maintenance-mode

#21
post #7

Is this not the best thing that could happen? Like now its in maintenance, it can be forked without any potential license change in the future, or any new features that are in that license change... This allows anyone to continue working on this, right? Or did i miss something?

Pretty sure you can’t retroactively apply a restrictive license, so that was never a concern.

Re: MinIO is now in maintenance-mode

#22
post #9

I thought they were pivoting towards close it and trying to monetize this? That got backlash so now it’s just getting dropped entirely? People get to do whatever they want but bit jarring to go from this is worth something people will pay for to maintenance mode in quick succession

> I thought they were pivoting towards close it and trying to monetize this?

That's literally what the commit shows that they're doing?

> *This project is currently under maintenance and is not accepting new changes.*

> For enterprise support and actively maintained versions, please see MinIO SloppyAISlop (not actual name)

Re: MinIO is now in maintenance-mode

#23
post #4

Hopefully no one is shocked or surprised.

I'm both shocked and not surprised. Lots of questions: Are they doing that bad from the outcry? Or are they just keeping a private version and going completely commercial only? If so, how do they bypass the AGPL in doing so, I assume they had contributions under the AGPL.

"For enterprise support and actively maintained versions, please see MinIO AIStor."

Commercial only, they will replace the agpl contributions from external people. (Or at least they will say that)

Re: MinIO is now in maintenance-mode

#25
post #7

Is this not the best thing that could happen? Like now its in maintenance, it can be forked without any potential license change in the future, or any new features that are in that license change... This allows anyone to continue working on this, right? Or did i miss something?

> ... it can be forked without any potential license change in the future ...

It is useful to remember that one may fork at the commit before a license change.

Re: MinIO is now in maintenance-mode

#26

Does anyone have any recommendations for a simple S3-wrapper to a standard dir? I've got a few apps/services that can send data to S3 (or S3 compatible services) that I want to point to a local server I have, but they don't support SFTP or any of the more "primitive" solutions. I did use a python local-s3 thing, but it was... not good.

You could perhaps checkout https://garagehq.deuxfleurs.fr/

Re: MinIO is now in maintenance-mode

#27
I've been using the minio-go client for S3-compatible storage abstraction in a project I'm working on. This new change putting the minio project into maintenance mode means no new features or bug fixes, which is concerning for something meant to be a stable abstraction layer

Need to start reconsidering the approach now and looking for alternatives

Re: MinIO is now in maintenance-mode

#28

Does anyone have any recommendations for a simple S3-wrapper to a standard dir? I've got a few apps/services that can send data to S3 (or S3 compatible services) that I want to point to a local server I have, but they don't support SFTP or any of the more "primitive" solutions. I did use a python local-s3 thing, but it was... not good.

rclone serve s3, could be.

Re: MinIO is now in maintenance-mode

#29

Does anyone have any recommendations for a simple S3-wrapper to a standard dir? I've got a few apps/services that can send data to S3 (or S3 compatible services) that I want to point to a local server I have, but they don't support SFTP or any of the more "primitive" solutions. I did use a python local-s3 thing, but it was... not good.

Check out from nvidia, aistore: https://github.com/NVIDIA/aistore

It's not a fully featured s3 compatible service, like MinIO, but we used it to great success as a local on-prem s3 read/write cache with AWS as the backing S3 store. This avoided expensive network egress charges as we wanted to process data in both AWS as well as in a non-AWS GPU cluster (i.e. a neocloud)

Post reply on HN