Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MinIO repository is no longer maintained

github.com

Post reply on HN
Print view View original

71–80 of 397 posts

Re: MinIO repository is no longer maintained

#71

Post by alexpadula »

muragekibicho wrote: post #18

I ran a moderately large opensource service and my chronic back pain was cured the day I stopped maintaining the project. Working for free is not fun. Having a paid offering with a free community version is not fun. Ultimately, dealing with people who don't pay for your product is not fun. I learnt this the hard way and I guess the MinIO team learnt this as well.

I don’t feel that way at all. I’ve been maintaining open source storage systems for few years. I love it. Absolutely love it. I maintain TidesDB it’s a storage engine. I also have back pain but that doesn’t mean you can’t do what you love.

Re: MinIO repository is no longer maintained

#72

Post by valyala »

If you are struggling with observability solutions which require object storage for production setups after such news (i.e. Thanos, Loki, Mimir, Tempo), then try alternatives without this requirement, such as VictoriaMetrics, VictoriaLogs and VictoriaTraces. They scale to petabytes of data on regular block storage, and they provide higher performance and availability than systems, which depend on manually managed object storage such as MinIO.

Re: MinIO repository is no longer maintained

#73

Post by StopDisinfo910 »

growse wrote: post #68
StopDisinfo910 wrote: post #48

Earlier quoted context omitted.

> then doing a bait-and-switch FOSS is not a moral contract. People working for free owe nothing to no one. You got what's on the tin - the code is as open source once they stop as when they started. The underlying assumption of your message is that you are somehow entitled to their continued labour which is absolutely not the case.

It's a social contract, which for many people is a moral contract.

Where is this mythical social contract found? I stand by my point: it's a software license, not a marriage.

Free users certainly would like it to be a social contract like I would like to be gifted a million dollars. Sadly, I still have to work and can't infinitely rely on the generosity of others.

Re: MinIO repository is no longer maintained

#74

Post by berkes »

einpoklum wrote: post #40
muragekibicho wrote: post #18

I ran a moderately large opensource service and my chronic back pain was cured the day I stopped maintaining the project. Working for free is not fun. Having a paid offering with a free community version is not fun. Ultimately, dealing with people who don't pay for your product is not fun. I learnt this the hard way and I guess the MinIO team learnt this as well.

> Ultimately, dealing with people who don't pay for your product is not fun. I find it the other way around. I feel a bit embarrassed and stressed out working with people who have paid for a copy of software I've made (which admittedly is rather rare). When they haven't paid, every exchange is about what's best for humanity and the public in general, i.e. they're not supposed to get some special treatment at the expe…

You can achieve something like this with a pricing strategy.

As DHH and Jason Fried discuss in both the books REWORK, It Doesn’t Have to Be Crazy at Work, and their blog:

> The worst customer is the one you can’t afford to lose. The big whale that can crush your spirit and fray your nerves with just a hint of their dissatisfaction.

(It Doesn’t Have to Be Crazy at Work)

> First, since no one customer could pay us an outsized amount, no one customer’s demands for features or fixes or exceptions would automatically rise to the top. This left us free to make software for ourselves and on behalf of a broad base of customers, not at the behest of any single one. It’s a lot easier to do the right thing for the many when you don’t fear displeasing a few super customers could spell trouble.

(https://signalvnoise.com/svn3/why-we-never-sold-basecamp-by-...)

But, this mechanism proposed by DHH and Fried only remove differences amongst the paying-customers. I Not between "paying" and "non-paying".

I'd think, however, there's some good ideas in there to manage that difference as well. For example to let all the customers, paying- or not-paying go through the exact same flow for support, features, bugs, etc. So not making these the distinctive "drivers" why people would pay. E.g. "you must be paying customer to get support". Obviously depends on the service, but maybe if you have other distinctive features that people would pay for (e.g. hosted version) that could work out.

Re: MinIO repository is no longer maintained

#75

Post by hobofan »

wvh wrote: post #36
PhilippGille wrote: post #3

They point to AIStor as alternative. Other alternatives: https://github.com/deuxfleurs-org/garage https://github.com/rustfs/rustfs https://github.com/seaweedfs/seaweedfs https://github.com/supabase/storage https://github.com/scality/cloudserver https://github.com/ceph/ceph Among others

Apart from Minio, we tried Garage and Ceph. I think there's definitely a need for something that interfaces using S3 API but is just a simple file system underneath, for local, testing and small scale deployments. Not sure that exists? Of course a lot of stuff is being bolted onto S3 and it's not as simple as it initially claimed to be.

SeaweedFS's new `weed mini` command[0] does a great job at that. Previously our most flakey tests in CI were due to MinIO sometimes not starting up properly, but with `weed mini` that was completely resolved.

[0]: https://github.com/seaweedfs/seaweedfs/wiki/Quick-Start-with...

Re: MinIO repository is no longer maintained

#76

Post by havnagiggle »

mickael-kerjean wrote: post #38
PhilippGille wrote: post #3

They point to AIStor as alternative. Other alternatives: https://github.com/deuxfleurs-org/garage https://github.com/rustfs/rustfs https://github.com/seaweedfs/seaweedfs https://github.com/supabase/storage https://github.com/scality/cloudserver https://github.com/ceph/ceph Among others

I'm the author of another option ( https://github.com/mickael-kerjean/filestash ) which has a S3 gateway that expose itself as a S3 server but is just a proxy that forward your S3 call onto anything else like SFTP, local FS, FTP, NFS, SMB, IPFS, Sharepoint, Azure, git repo, Dropbox, Google Drive, another S3, ... it's entirely stateless and act as a proxy translating S3 call onto whatever you have connected in the oth…

I was looking at running [versitygw](https://github.com/versity/versitygw) but filestash looks pretty sweet! Any chance you're familiar with Versity and how the S3 proxy may differ?

Re: MinIO repository is no longer maintained

#77

Post by philipwhiuk »

PhilippGille wrote: post #3

They point to AIStor as alternative. Other alternatives: https://github.com/deuxfleurs-org/garage https://github.com/rustfs/rustfs https://github.com/seaweedfs/seaweedfs https://github.com/supabase/storage https://github.com/scality/cloudserver https://github.com/ceph/ceph Among others

To be clear AIStor is built by the MinIO team so this is just an upsell.

Re: MinIO repository is no longer maintained

#78

Post by PunchyHamster »

StopDisinfo910 wrote: post #48
jbstack wrote: post #27

Earlier quoted context omitted.

There's nothing wrong at all with charging for your product. What I do take issue with, however, is convincing everyone that your product is FOSS, waiting until people undertake a lot of work to integrate your product into their infrastructure, and then doing a bait-and-switch. Just be honest since the start that your product will eventually abandon its FOSS licence. Then people can make an informed decision. Or, if…

> then doing a bait-and-switch FOSS is not a moral contract. People working for free owe nothing to no one. You got what's on the tin - the code is as open source once they stop as when they started. The underlying assumption of your message is that you are somehow entitled to their continued labour which is absolutely not the case.

it's still a bait and switch, considering they started removing features before the abandonment.

Re: MinIO repository is no longer maintained

#80

Post by mickael-kerjean »

havnagiggle wrote: post #76
mickael-kerjean wrote: post #38

Earlier quoted context omitted.

I'm the author of another option ( https://github.com/mickael-kerjean/filestash ) which has a S3 gateway that expose itself as a S3 server but is just a proxy that forward your S3 call onto anything else like SFTP, local FS, FTP, NFS, SMB, IPFS, Sharepoint, Azure, git repo, Dropbox, Google Drive, another S3, ... it's entirely stateless and act as a proxy translating S3 call onto whatever you have connected in the oth…

I was looking at running [versitygw]( https://github.com/versity/versitygw ) but filestash looks pretty sweet! Any chance you're familiar with Versity and how the S3 proxy may differ?

I did a project with Monash university who were using Versity on their storage to handle multi tiers storage on their 12PB cluster, with glacier like capabilities on tape storage with a robot picking up data on their tape backup and a hot storage tier for better access performance, lifecycle rules to move data from hot storage to cold, etc.... The underlying storage was all Versity and they had Filestash working on top, effectively we did some custom plugins so you could recall the data on their own selfhosted glacier while using it through the frontend so their user had a Dropbox like experience. Depending on what you want to do they can be very much complimentary
Post reply on HN