MinIO stops distributing free Docker images

You suddenly deciding that you won't be offering updated Docker images especially after a CVE and with no prior notice (except a hidden commit 4 days ago that updated the README) is approaching malicious-level actions.

If they truly cared about their community and still wanted to go through the decision of not offering public docker builds the responsible thing to do is offer a warning period, start adding notices in the repo (gh and docker) and create an easy migration path, even endorse or help some community members who would be fine with taking care of the public builds of the image.

But no, they introduced the change, made no public statement about it, waited for someone to notice this, offered no explanation and went silent. After a huge CVE. Irresponsible.

thats entitlement but seen from the other side.

I do concede that they could’ve done a better job communicating these changes. But they don’t have to.

Building minio is not only trivial, but is standard procedure - the latest release is in my distributions standard package repo, and they would not use prebuilt binaries. If you want that dockerized, the Dockerfile is shorter than the command-line to run said container. Dealing with Docker themselves, the corporation that has famously gone on a tax collection spree, is however quite the pain in the arse for a company.

I can't stand the entitlement people (everyone, not one particular person) feel when they are provided things for free. Sure, minio is run by a corporation these days and this applies a bit more to smaller FOSS projects, but the complaint is that the silver spoon got replaced with a stainless steel one. You're still being fed for free, despite having done nothing for it.

</rant>

That expectation does not entitle anybody to anything though.

> people will rely on that and will chose your software based on that expectation

That is their decision. Without any contract or promise, there is no obligation to anybody.

> You suddenly deciding that you won't be offering updated Docker images […] is approaching malicious-level actions.

I really don’t get this entitlement. “You are still doing unpaid work I benefit from, but you used to do more, therefore you are malicious.” is something I really cannot get behind.

There's also nothing wrong in being upset about something you relied on disappearing overnight. If someone decides to provide something for free, they should give time for people to stop relying on this free stuff if they can.

However, I also believe you should own it if you decide to ever rely on prebuilt Docker images. More specifically, if you are relying on prebuilt Docker images, you are letting someone else decide on a part of your infra. And yes, this someone else can decide to stop providing this part of your infra overnight. This is on you.

I also don't find anything wrong in deciding to not provide binaries for your open source project, or to stop providing binaries, including docker images.

Coolify is already doing it but your comment is on the verge of being passive agressive. I wouldn't say these are open source freeloaders because they could be using things like watchtowers etc. which automatically update and it could be a very huge deal for automated updates especially after I saw that some recent CVE of minio happened.

Simply put this just hurts the security of people running minio, I wouldn't say its freeloading, its actively harming the community. There are people in that thread who are paid customers as well saying that they lost a customer. I wouldn't say its freeloading. Minio already has some custom license or paid offering and I think that they make decent enough money out of it, providing docker files and then stopping to is kinda a shitty behaviour if they are unable to explain the reasons exactly why. I couldn't find the exact reasons on why they are doing what they are doing except making it hard for people to self host.

Agree. But that's not my point. If you start an oss project from scratch and you don't want to provide builds that's fine.

If you start your oss project, provide public docker images since the beginning, start getting traction, create a commercial scheme for you to monetize the project and then suddenly make a rug pull on the public builds; that is indeed irresponsible, and borderline malicious when you do it without: 1. sufficient warning time. 2. after a recent cve.

Is it malicious? I don't know. I prefer to believe in Hanlon's razor. Is it irresponsible? 100% yes.

Sounds exactly like freeloading to me. You may think of that term negatively, but it is exactly what it is.

For example:

"You are joking ?!

The commit about source only is 4 days old (9e49d5e)

We are currently paying for a license while using the open source version, you already removed the oidc code from UI console and now docker images. We are not happy by this lock-in. We will discuss this internally, but you may loose a paying customer with this behavior."

- if you rely on something, you should make sure you can reasonably rely on it (indeed, for instance by paying someone)

- if you provide something, even for free, you should expect people will rely on it and you shouldn't pull the plug overnight if you can help it (of course, if you run out of business or something bad happens to you, that's something else). There is some kind of implicit commitment. Nobody should be entitled to receive free pre-built Docker images, but OTOH what's the point of even providing pre-built Docker images if you expect people not to rely on them? This feels pointless and you probably shouldn't start providing them in the first place if you have this expectation.

This is true legally, but not otherwise (socially, practically)

"That is their decision. Without any contract or promise, there is no obligation to anybody."

Again, true legally, but IMHO a really silly position to take overall.

Imagine I provide free electricity to everyone in my town. I encourage everyone to use it. I do it all for free. I'm very careful to ensure the legal framework means i have no obligation, and everyone knows i have no obligations to them legally. They all take me up on it. All the other providers wither and die as a result. 15 years later, i decide to shut it all down on a whim because i want to move on to other things. The lights go out for the town everywhere.

Saying "i have no legal obligations" is true, but expecting people to not be pissed off, complain, and expect me to not do this is at best, naive.

Calling them entitled is even funnier. It's sort of irrelevant if they are entitled or not, after i put them in this position.

Legal obligation is not the only form of obligation, and not even the interesting ones most of the time.

More importantly - society has never survived on legal obligation alone.

I do not think you would enjoy living in a world where legal obligation is the only thing that mattered.

Maybe a car analogy (because they hardly work). It's like lending your car to someone everyday then stopping, then the person complains that they have no way to get around. But there is walking, biking, busses or buying your own car.

> One who does not contribute or pay appropriately; one who gets a free ride, etc. without paying a fair share.

Which I believe is a bit more generic (giving back might not be the only way of being fair).

> You may think of that term negatively

But the term carries a negative judgement, what's the point of this term otherwise? Without the judgemental part, you'd just say "using for free" or something.

The whole question is: is it fair to use open source software for free?

And I believe it is. Actually, this is stronger than this: I believe people should feel free to use free software for free, and should not be looked down for doing so. This is key for freedom 0 to be an actual thing. (I'm not set in stone in this position and would be happy change my mind on this though).

The notion of "giving back" can be discussed. I believe it is fair to get stuff from Person A for free and then helping B for free (later or earlier), in the hope that some person P will eventually help / have helped Person A for free for instance - this has the potential to provide everyone with a strong, helpful society and it would be even more enjoyable and reliable than a society that enforces pair to pair transactions.

Indeed, if someone always takes stuff for free and never contributes to anything, I would find this unfair (unless for some reason they can't contribute back, because of a disability or something). I would call this freeloading. Society cannot work like this. But you need the bigger picture to assess this.

When you start to try thinking about all this, the concepts of giving back, fairness, etc, it gets quite complicated. You also need to take in account the way society and the economical system works as a whole. What are the incentives, the motives, etc?

Basically, qualifying someone as a "open source freeloader" without context just because they use freedom 0 without paying is quite bold and might not be fair.

What if a company uses MinIO for free but provides some nice open source software?

Just don't judge someone too fast.

[1] https://en.wiktionary.org/wiki/freeloader

I hate to break it to you, but you know the CVEs are fixed in the source code, not in the Docker Image? Just build it yourself, the good folks have even provided a Dockerfile for it.

It is more like you went around your neighborhood and turned peoples lights on in the evening, then stopped.

Sure, it’s a lost convenience, but people can easily choose to just… push the button themselves. Or pay somebody to continue doing it for them. Or get a timer.

It’s really not a big deal, and there are plenty of alternatives.

Does it make you less frustrated to remember that humans are pattern recognition machines and our existence is essentially recognising and adapting to patterns, and so when someone does something repeatedly - regardless of if they're doing it for free - humans will recognise a pattern and adapt to it.

This is an inevitable consequence of coexisting with humans: if someone does something repeatedly, it creates an expectation. This is how learning works. If someone stops doing something, people are going to mention the consequences of their expectation not being met. Framing that as entitlement doesn't seem productive, especially in situations like this where it looks like the change wasn't properly communicated.

I don't think there can be a world where humans are able to learn/adapt/be efficient whilst not having expectations.

I believe there could be a world where people don't get pejoratively labelled as entitled for expressing the inconvenience caused by having functionality removed.

So many commenters are just plain rude. They got free value for along time. Someone giving the free value decides to allocate their time otherwise. And the long-time receivers of the free value now cannot behave.

And you seem to make excuses for them...

It's just rude to behave like that after having enjoyed gifts for so long. They behave like spoiled children. Nothing to defend IMHO.

Do you know their reasons for discontinuing? Are you even entitled to know that? It's their private matter.

> of course, if you run out of business or something bad happens to you, that's something else

Huh? So now everyone should let you know "it was out of their hands"? You have no idea how entitled you behave.

> There is some kind of implicit commitment.

No. That's just between your ears. It's putting fancy words on a feeling you have, not something that actually exists.

> what's the point of even providing pre-built Docker images if you expect people not to rely on them?

How do you know they had that expectation? And why do you care?

> This feels pointless and you probably shouldn't start providing them in the first place if you have this expectation.

You are excusing yourself for these commenters that behave like spoiled children: not thankful for what they got for free, but only bitching when it stops.

Of course many creators are selfish. Once they have benefitted from everyone using their project they think: we want more. Then the rugpulls start. They think they no longer need their users, so now they can abuse them for additional profit.

> Do you know their reasons for discontinuing? Are you even entitled to know that? It's their private matter.

Fully addressed in the "if you can help it" part of my comment.

> You have no idea how entitled you behave.

I have 100% idea how entitled I behave. I don't at all. I don't use MinIO. As an employee, I push internally for relying on our own infra (but we are quite good at this already).

I don't expect open source projects to provide binaries. Well, I kinda do if they've been doing it though. Expectations vs entitlement? Not the same thing.

We're discussing human interactions and expectations here.

---

So, in your opinion, what's the point of providing pre-built binaries if you don't want others to be able to rely on them then?

As someone who develops free software in my hobbies and also as an employee, if I provide binaries for free, I 100% expect people to be able to rely on them, or I just don't do it, and I would 100% feel like I'd be causing them issues by stopping doing it on short notice. I would feel like I'd owe them explanations (and their can be valid ones I'm sure - burn out would be a hell of a valid explanation to stop working on the projects at all) if I did that. They'd not be entitled to receive the binaries from me, but they would expect it and breaking expectations is not very nice. I have difficulties seeing this another way to be honest.

Let's also recall that we are talking about a project who's business might have benefited from the adoption in the first place.

> why do you care?

I could care about nothing, but that's not what I'm on HN for. I'm curious and interested.

You can read more about my views on this stuff here if it can help understand me: https://news.ycombinator.com/item?id=45667271

Then Minio decided to disable the feature to upgrade the lightbulb automatically, the code to update it is still there, they just don't want to do it anymore. Conveniently there is a Minio+ enterprise plan that has this feature. But hey! they tell you that you can easily set up your own server to update your lightbulb automatically. And most enterprise clients or people who have Minio lightbulbs in their office will do that.

But for single enthusiasts who don't have a server because they are just running a Minio lightbulb in their shed it's a bad situation, because if they knew this from the beginning they would have gone with another free lightbulb that updated automatically.

In short: Minio has the legal right to do whatever they want, people using minio have the right to be pissed. It's an all around bad publicity stunt and if I was a Minio investor I would really wonder why they are trying to piss off their loyal user base for a quick buck.

What keeps those enthusiasts from setting up a scheduled GitHub Action (or whatever system they prefer to use) to build the image for themselves?

How much (amortized) effort are we actually talking about here? One minute per release?

When a restaurant which you've been going to for years one day decides to serve you your favorite meal with a bit of poop on the side, do you not have the right to be upset about it? They're not under any obligation to serve you meals you're happy with. There was no contract or promise. The fact you're paying for their service doesn't buy you these rights either. Those are just the terms of service both parties have agreed to.

Similarly, open source software is much more than a license. There is a basic social contract of not being an asshole to users of your product, which is an unwritten rule not just in software and industry in general, but in society as a whole. The free software movement is an extension of this mindset, and focuses on building software for the benefit of everyone, not just those who happen to pay for it, or those who meet your specific criteria. Claiming you support this philosophy, while acting against it, is hypocritical, and abusive towards people who do believe in it. And your point is that that people who complain about this are entitled? Give me a break.

If you want to place restrictions on how your software is used and who gets to enjoy it, that's fine, but make those terms explicit by choosing the appropriate license and business model from the start. Stop abusing OSS as a marketing tactic.[1]

[1]: https://news.ycombinator.com/item?id=45666757

With this the solution becomes obvious. You select piece of technology to build on you are fully and ready to take over it for purposes you want to use for it. The code is shared and you should not expect anything more.

If there had never been an offer, they would not have built around it, and would have found another solution and, even if harder or more inconvenient, learned how to use that and built around that. Sure, no one is obligated to continue to provide them with the product, but saying that they are being unreasonable for expecting a little bit of warning time before having support pulled is a bit unrealistic.

I know we have done the metaphors to death already, but let's try another one: imagine if someone gave you a ride to work every day for years and one morning they didn't show up and you couldn't get in touch with them. You should have had a backup plan, and you shouldn't have depended on them, but it will take you a while to find a car and rearrange your schedule and learn how to drive or whatever you have to do, and all they had to do was notify you a month or two earlier that they wouldn't be able to do it anymore.

Note that a CVE is not an indication that something doesn't work. In the real world, they're mostly relevant only for businesses that need something like PCI compliance. Especially for something like a storage server that shouldn't be directly exposed to the Internet. If you are a business that has some compliance obligation, you have no one to blame but yourself if you rely on others' charity to meet that obligation.

I don't get why one they would provide prebuilt binaries in the first place, and removing them is just cleanup.

But MinIO didn't do any of that. They're still a 100% open-source project, with the proper license.

In this case, we're not even talking about that though, it's just a redundant prebuilt binary getting janked. I don't think it makes sense to provide prebuild binaries in the first place.

It certainly does. In the UK and many other countries (possibly not the US), as soon as you are paying for a good or service you are entitled that it is satisfactory quality, fit for purpose and as described. I think it's uncontentious that a meal at a restaurant that includes poo is not satisfactory quality. Businesses have less rights than consumers but this would still count. However, the restaurant is certainly free to refuse serving you at all (unless they're it's because of a protected characteristic e.g. because of your race or gender).

I'm not sure how much that affects your analogy since it was probably a bit too far removed from the original situation to be useful anyway.

Without other elements, it's definitely not nice to stop releasing the binaries out of the blue, especially for a security fix. To me it's purely a question of breaking expectations you've built yourself (I don't mean entitlement, I mean expectations).

Now, it's indeed not the end of the world, and:

> you have no one to blame but yourself if you rely on others' charity to meet that obligation

100% agree with you on this (that's my first point in my original comment).

> That is their decision. Without any contract or promise, there is no obligation to anybody.

Not everything is legally enforced. Open source is a social phenomenon. Why are you so surprised that these social rules are being enforced socially?

There are obligations... it's how society functions.

> I really don’t get this entitlement. “You are still doing unpaid work I benefit from, but you used to do more, therefore you are malicious.” is something I really cannot get behind.

I really don't get this entitlement. You expect that nobody should follow any social contracts and I'm sure are always surprised when people call you out for being asocial.

No. There is no valid justification, and the suggestion otherwise suggests a lack of understanding of what exactly these rude individuals are demanding.

The very least people can do when receiving such quite extensive voluntary favors and dedication from others is to be polite and show proper gratitude and appreciation. Otherwise, they are not worth the personal and uncompensated sacrifice of time (a quite non-renewable reosurce) and personal health required for the support. They are not even worth the stress or brain cycles required for communication.

(Not saying there aren't plenty of people showing appreciation - otherwise we would have given up on FOSS entirely a long time ago - just talking about those that don't)

There are a lot of paragraphs in this thread laying the groundwork for this subtle strawman, but neither you nor DannyBee are addressing the real opposing position. That's the one that says there is no legal obligation and there is no social obligation. You're both treating the latter as if agreement about its existence is a forgone conclusion not in dispute. But of course it's in dispute. It's the basis of the dispute.

In the end, it’s just software made available under specific terms. While I understand the inconvenience for users if things change, it feels like part of the disappointment might stem from one-sided expectations.

Then there are ideological reasons: Purposly trying to make the open source version sustainable.

And then reduced lockin etc. by not using Enterprise only features by accident/convenience, which leaves the door open to leave the contract.

Of course the entitlement to volunteer work is also rude, and in my opinion worse.

Don’t like it? Stop being a parasite and pay someone for a support contract.

You're essentially saying that only users who contribute to OSS are worthy of attention and support. This is no different than saying that only commercial users, or those from specific countries, backgrounds, or industries are worthy of the same.

Those users who create issues, request features, and, yes, ask for support, are as valuable as those who contribute code or money. They're all part of the same community of users that help build a successful product. And they do it for free for you, because they're passionate about the product itself.

If you think otherwise then you should make your terms of service explicit by using a restrictive license and business model. OSS is not for you.

Yes, some people can be rude, demanding, and unworthy of your attention. But you make those boundaries clear, not treat all non-paying users as entitled children.

Of course there is. Which is why many hostile projects get forked.

"That is the beauty of OSS", I hear you say. And I agree, but most people aren't developers. Even those who are, might not be familiar with the technology to continue maintaining the project. And even those who are, will still need time and effort to understand the codebase at a level that they're comfortable with maintaining it. And even those who are interested in all of that, might not do a good job at it.

So, ultimately, it is a very small subset of users who would not only have the capability to continue maintenance, but would manage to do as well as the original maintainers for the benefit of the entire community.

Most people saw an interesting piece of software, gave it a try and enjoyed it, and, if the project is successful, would probably like to continue using it. When the original developer ignores or is actively hostile towards these users, you're saying that they have no right to be upset about it? That's what I find ridiculous.

Yes, some people can be demanding and annoying, but that's true regardless if they're a paying customer, a contributor, or a "freeloader". The way you deal with this is by communicating and setting clear boundaries, not by alienating your user base.

True in theory but no one has infinite time to distinguish correctly between good feature requester or bad one.

The GP didn't say it entitled them to anything, but that it created a sense of entitlement. You are correct there's no contractual obligation to do so, but it was likely a part of the decision to go with their solution, i.e. "they make it easy to deploy!". It is a very logical conclusion to say "they just made it HARDER THAN BEFORE to deploy".

Promises are not always explicit written permission; that's why I got in trouble for re-broadcasting major-league baseball with only implicit verbal permission (thanks, Simpsons!)

The point is, there is a community project, and Minio has revealed they are leaving the community. It's not illegal that they do so, any more than divorce is illegal, but it's concerning to anyone who views themselves as part of that community.

It raises a point that is it smart to join a new community that depends on the same people or organization.

Your persistent inability to comprehend this makes you look like a poor candidate for future professional collaboration. Maybe you are autistic, maybe just a shill, but it's not helping you.

Seems like the new definition of open source is not license, not code but What I need others must do for me

No, it doesn't. Yes, there are general safety regulations in any country, but there are no hard rules as to what "satisfactory" or "fit for purpose" means.

My analogy was contrived to make a point. Of course serving actual feces is not "satisfactory". But I imagine that you can extrapolate my analogy into an infinite number of possibilities where someone who once enjoyed certain services or products can find them not "satisfactory" anymore. That is a commonplace situation in any marketplace, and it is perfectly valid for the person on the receiving end to be upset about it.

The one hole you can poke at my analogy, which I anticipated, is that there is (typically) no financial transaction between users and developers of free software. But my response to this is that a financial transaction is not a requirement for the social contract to be established with users of any product or service, regardless of its distribution or business model. Those users can still expect a certain level of service, and understandably so. This expectation exists whether the person is a customer or not.

A closer analogy might be a community kitchen, or garden. But it really makes no difference to my argument.

The free software philosophy is agnostic to how software is monetized. It's true that it is more difficult to do so than with proprietary software, but it's certainly not impossible. Many companies have been built and thrive on producing free software. The crucial thing, regardless of the business model, is to treat all your users with the same amount of respect, dedication, and honesty. The moment you stop doing that, don't be surprised when the community pushes back. That's on you, not on "entitled" users.

Then I decide to stop. It doesn't really matter why, I wasn't getting paid or had not made any sort of formal agreement or promise, I just don't want to do it anymore. Now I shovel my sidewalk to the property line exactly and that's it. Hey, that's my legal obligation; I don't need to do any more! Mr. Johnson now has a lot more trouble getting out of his house; we see him a lot less. The baby is crying while new mom slips around trying to load up strollers and diaper bags and a car seat. The snowbirds just got fined by city bylaw for not clearing their walk. That dad's school trip is just a little longer, colder and unpleasant.

Hey, this isn't my fault! All those people took my effort for granted; I never promised to shovel their walks! They have no basis to judge me! But you better believe that this decision reduced their assessment that I'm a "good neighbour". Community is built mostly on implicit agreements, norms and conventions that are established through practice & conduct over time. You're arguing the right/wrong of this in the face of legal formalizations, while others are just saying it is a fact, not weighing the benefits and obligations.

Not all shitty behavior is governed by contracts and licenses. You can be an asshole without violating the terms of a license.

FOSS licenses already do that: they shout at you in all-caps that the authors PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED.

Meanwhile the licenses don't say anything about communities.

For better or worse, OSI convinced everyone that "open source" is synonymous with using specific licenses that meet their definition. If that's the case, then how can it be a "fundamental misunderstanding of OSS" to strictly interpret OSS by the terms of the licenses, which don't mention any sort of "social contract", while they do include language explicitly contrary to such expectations of users?

Recently switched from bitnami to minio here, with plenty heads up & they scheduled brown outs etc, along with legacy images to fallback on for users who don't get informed by anything until image gone

A feeling of a community is not a contract. Complaining about losing that community changes nothing; and I believe that's the point GP is making.

Like I said, the fact that people are human, and that minios did a thing repeatedly, is why the expectation is there. Saying it's not justified is like saying the sky isn't justified being blue, getting upset and frustrated about it is even more silly.

There's no need for people to be rude, I agree, but I don't really see any people being disproportionately rude in their comments, especially in the context of a provider who pulled part of their provisions without fair warning.

I see GGP's comment attitude all too frequently on the internet ("nobody is entitled to anything") as the default. Which is such a nasty connotative strawman, it's kind of absurd. But hey, that's the internet for you.

I don't think this is a reason to never volunteer but you have to develop a thick skin, know where your lines are, and at some point politely but firmly say "no."

And yet, most people who do decide to share their work in public, directly or indirectly reap the rewards of it. They get exposure and recognition, which in turn opens many doors. I'm not saying that exposure alone puts food on the table, but it's certainly not entirely negative. Many people would envy to be in that position.

Your analogy is akin to any public figure enjoying their work, but not enjoying the attention. That certainly happens, but the attention, and all its negative aspects, comes with the territory. That attention might even be partly responsible for getting them to where they are. People in such line of work must learn to live with their choices. Not be surprised when their audience has certain demands and expectations, which may or may not be within reason.

They didn’t do it last year. I was disappointed, but I’m not angry at them. I realize that they were spending a lot of time and energy and maybe they are just burned out.

I’m sure there are people who are angry and judge them. But those people are spoiled, entitled brats.

The distinction is that it is entirely fine to be disappointed. It’s not fine to get angry.

Because free and open-source software is more than a set of licenses approved by some governing body.

It is part of a social movement and ideology pursuing the open sharing of knowledge, and building communities around this where everyone can benefit, not just a select few. Software is one aspect of this, due to its roots in the hacker counterculture of the 1970s, but the core idea extends beyond it.

You can read more about this in many places. Bruce Perens specifically refers to a "social contract" in this early post[1] on the Debian mailing list. This is what is usually referred to as the "spirit" of open source, and is not strictly encoded in any official definition. The success of OSS depends on implicit mutual trust and respect, not on explicit rules and licenses.

[1]: https://lists.debian.org/debian-announce/1997/msg00017.html

Sure but maybe the changed their mind or just got burned out.

But that is not what happened in the case of MinIO, and many other projects. They deliberately removed features from the software, and made it more difficult to use. They prioritized working on their commercial product, and used the "community edition" as a marketing funnel for it. This is what I'm objecting to.

In any case, I've made my point clear, and don't like repeating myself. Cheers!

so its a communications issue? if minio or whoever explains this, OK. that's not what happened, so it's not what happened.

Someone still can. They can't revoke the AGPL license of previous versions.

>They prioritized working on their commercial product

It's a company, not a non-profit. What else would you expect them to do?

I'm less understanding when a VC backed company does things like this, but many times its just a matter of "we were trying to make money by doing X. X is no longer working, so we're moving to Y".

I've also seen hostile mobs form when very small companies or individuals decide to start charging for things they used to give away for free, so it's not just that they are a VC backed company here.

This is the tragedy of the commons but not just for a field of grass, instead its for all human altruism. You really need to think about the consequences of this attitude because it doesn't lead where you seem to think it leads. In fact, it leads to exactly the opposite set of human behaviors.

PS The neighbors could easily just contract someone else to do the shoveling in the future and instead of being salty about having to pay, looking at it as how much money they saved in the past.

If I host a code repo on an otherwise static site, with no ability to contact the author or engage in a community, it is still widely considered "open source" if it uses an OSI-approved license.

Likewise if I host the same code repo on Github and disable issues and set the pull request template to say "All PRs will be closed and I will shout expletives at you for wasting my time", if it uses an OSI-approved license then it is still open source per the OSI's own definition.

> That expectation does not entitle anybody to anything though.

Note that implied contracts do exist, and sometimes expectations based on prior conduct do suffice to form an enforcable contract. In this case, I don't know whether you can reasonably make that argument, but that's never stopped enterprising lawyers before.

https://en.wikipedia.org/wiki/Implied-in-fact_contract

People submitting PRs aren't freeloaders: they are building the product for you. People filing bug reports aren't freeloaders: they are helping you solve the bugs in your code. People writing blog posts about setting up MinIO aren't freeloaders: they are writing documentation for you. People holding talks about it at conferences aren't freeloaders: they are essentially doing free marketing for you. Even someone leaving a "thumbs up" on a Github issue isn't a freeloader anymore!

MinIO is also screwing over those active contributors, who are volunteering their time to improve the value of MinIO's product. That's not just "no longer helping freeloaders", that is "actively hurting the community".

Besides, I'm sure the community has plenty of people who would be more than happy to volunteer time to build Docker images. Do you really think MinIO is going to let them publish it under the official "minio/minio" name so the community can still benefit from it without MinIO having to "support freeloaders", or do you think there could be an ulterior motive behind nuking the image - such as pushing people to the paid version?

That has got to be the most fallacious analogy I've seen in a long time, and that's ignoring the fact that serving poop would get you in serious trouble in most jurisdictions. "False equivalence" barely covers it.

There is a basic social contract of not being an asshole to users of your product

Nope, nope...you win. Even more fallacious. Being an asshole to your users is a meme in OSS it's so common. Someone should tell that Linus guy about this 'social contract' he agreed to and signed that he's in violation of. /s

Claiming you support this philosophy, while acting against it, is hypocritical, and abusive towards people who do believe in it.

You think there's a philosophy. Some other people here do. There is no consistent OSS philosophy. There wasn't back when Stallman was thinking "what should I call this thing that is Not Unix" and there isn't today. If that was remotely true we'd still be happily using GPLv2. Because at the end of the day there is what is written in the license, and then there is wishful thinking. Sometimes wishful thinking results in nice things, and sometimes...well...here we are.

If you want to place restrictions on how your software is used and who gets to enjoy it, that's fine, but make those terms explicit by choosing the appropriate license and business model from the start.

Ignoring the laugh-out-loud silliness of "you should pick all these things about your startup day #1 and NEVER CHANGE THEM", exactly what terms of their OSS license did they violate? Be explicit. Don't wave your hand and say "but social contract that doesn't exist!", "but philosophy I made up and want to apply to people who didn't agree to it!". Because a license only means what's written down in it, not what we want it to mean. I get that you think there should be a "No assholes, we'll never, ever pivot to meet market changes and we pinky swear we won't rug pull on you" license that people should be forced to use, but I don't think to many people will sign up for it. See: GPLv2.