Lmao, that was fast.
MinIO repository is no longer maintained
161–170 of 397 posts
Re: MinIO repository is no longer maintained
#162I 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.
If your main motivation creating/maintaince a popular open source project was to make money then you don't really undersand the open source ethos.
Even if motivation isn't about making money, people still need to eat, and deal with online toxicity.
Re: MinIO repository is no longer maintained
#163I 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.
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…
The only meaningful informed decision, but sadly much less known (and I think we should talk and insist more on it), is to be wary if you see a CLA. Not all do, but most perform Copyright Assignment, and that's detrimental to the long-term robustness of Open Source.
Having a FOSS license is NOT enough. Idealy the copyright should be distributed across all contributors. That's the only way to make overall consensus a required step before relicensing (except for reimplementation).
Pick FOSS projects without CLAs that perform Copyright Assignment to an untrusted entity (few exceptions apply, e.g. the FSF in the past)
Re: MinIO repository is no longer maintained
#164Earlier quoted context omitted.
That means that any project without the letters "AI" in the name is dead in the eyes of investors. Even plain terminals are now "agentic orchestrators": https://www.warp.dev
Are investors really that gullible? Whenever I see "AI" slapped onto an obviously non-AI product, it's an instant red flag to me.
Are you kidding me
"Long Island Iced Tea Corp [...] In 2017, the corporation rebranded as Long Blockchain Corp [...] Its stock price spiked as much as 380% after the announcement."
Re: MinIO repository is no longer maintained
#165I 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.
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…
> Just be honest since the start that your product will eventually abandon its FOSS licence.
How does this look? How does one "just" do this? What if the whole thing was an evolution over time?
Re: MinIO repository is no longer maintained
#166Earlier quoted context omitted.
> 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 o…
I think this is a good point and a true point.
However, I understood GP's mention of "embarrassment" to speak more to their own feelings of responsibility. Which would be more or less decoupled from the pressure that a particular client exerts.
Re: MinIO repository is no longer maintained
#167Has anybody actually tried AIStor ? Is it possible to migrate/upgrade from a minio installation to AIStor ? It seems to be very simple, just change the binary from minio to aistor: https://docs.min.io/enterprise/aistor-object-store/upgrade-a...
Is AIStor Free really free like they claim here https://www.min.io/pricing, i.e
Free
For developers, researchers, enthusiasts, small organizations, and anyone comfortable with a standalone deployment.
Full-featured, single-node deployment architecture
Self-service community Slack and documentation support
Free of charge
Re: MinIO repository is no longer maintained
#168Earlier quoted context omitted.
it's not about the money. for large open source projects you need to allocate time to deal with the community. for someone that just wants to put code out there that is very draining and unpleasant. most projects won't ever reach that level though.
> it's not about the money OP sure makes it sound like it's about the money. > for someone that just wants to put code out there that is very draining and unpleasant. I never understood this. Then why publish the code in the first place? If the goal is to help others, then the decent thing would be to add documentation and support the people who care enough to use your project. This doesn't mean bending to all their…
The person "throwing" the software has 0 obligation to any potential or actual users of said software. Just the act of making it available, even without any kind of license, is already benevolent. Anything further just continues to add to that benevolence, and nothing can take away from it, not even if they decide to push a malware-ridden update.
There is obligation to a given user only if it's explicitly specified in a license or some other communication to which the user is privy.
Re: MinIO repository is no longer maintained
#169I 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.
Completely different situations. None of the MinIO team worked for free. MinIO is a COSS company (commercial open source software). They give a basic version of it away for free hoping that some people, usually at companies, will want to pay for the premium features. MinIO going closed source is a business decision and there is nothing wrong with that. I highly recommend SeaweedFS. I used it in production for a long…
> > 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.
> Completely different situations. None of the MinIO team worked for free. MinIO is a COSS company (commercial open source software).
MinIO is dealing with two out of the three issues, and the company is partially providing work for free, how is that "completely different"?
Re: MinIO repository is no longer maintained
#170They 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
from my experiences rustfs have promise, supports a lot of features, even allows to bring your own secret/access keys (if you want to migrate without changing creds on clients) but it's very much still in-development; and they have already prepared for bait-and-switch in code ( https://github.com/rustfs/rustfs/blob/main/rustfs/src/licens... ) Ceph is closest feature wise to actual S3 feature-set wise but it's a lot t…
> [rustfs] have already prepared for bait-and-switch in code
There's also a CLA with full copyright assignment, so yeah, I'd steer clear of that one: https://github.com/rustfs/rustfs/blob/main/CLA.md