321–330 of 585 posts
Earlier quoted context omitted.
Metaphor I often see in FOSS. You are this hobby painter sitting every morning on Monmartre square in Paris, painting. It attracts people's eyes. They love your work and you become a sensation, going viral. Instagram influencers from around the world just need you in their picture, they say. You just shrug and paint. One day you got bored of Monmartre. Of pleasing the crowds. You want rest, a spot in nature to paint…
If the painter doesn't enjoy painting in public, then they should've picked a quiet spot in nature in the first place. 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 en…
Sure but maybe the changed their mind or just got burned out.
Earlier quoted context omitted.
> If you were given the ratchet and then someone wanted to charge you every time you use it you would also be pissed. People gotta eat. If someone's making valuable tools and giving them away, they still need to get paid somehow. If people aren't voluntarily tipping them enough, then something's gotta give. There have been too many stories of open source developers basically burning themselves out for years, then it…
if people are giving away wrenches and not getting paid for that, they will quickly run out of wrenches, and they will learn. giving away something free does not inherently give them the right to charge for use of the wrench. giving a wrench to someone where you charge based on usage should be something that is agreed upon up front, not at some point later, after a rug is pulled out from under the customer.
You're mixing up non-capitalist kindness and reciprocity relations with market relations. They're different things. Downloading open source code doesn't make you anyone's "customer."
The thing that happens first with these "open-source gone closed stories" is the community (or one particularly big mooch) failed to reciprocate the developer's efforts or was otherwise undercutting them. Then the developer responded.
And of course, the predictable response from some parts of the community is "how dare you not let me mooch off your efforts forever. I am entitled!1! Protection racket! Rug pull!"
Earlier quoted context omitted.
> half the price of S3 No one other than hobbyists is paying full price on AWS.
How to not pay full price on AWS? We pay $10K+ per month and nobody gives us any discount.
Earlier quoted context omitted.
If the painter doesn't enjoy painting in public, then they should've picked a quiet spot in nature in the first place. 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 en…
> If the painter doesn't enjoy painting in public, then they should've picked a quiet spot in nature in the first place. 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!
Earlier quoted context omitted.
> I wonder if they will be "valkeyed"? Not by AWS presumably Almost certainly not, due to the AGPL license. I know Nutanix got into hot water about distributing Minio so I don't think any big shop will fork it.
Nuantrix distributed a version that was still Apache licensed and merely failed to disclose they had made changes. This is after MinIO asserted that Weka had also stolen their AGPL-licensed code, showing that they extracted binaries from the distribution. They forgot that that 3-month old (unmodified) version was still Apache licensed though. MinIO generally don't seem to consult lawyers often. They haven't even set…
Earlier quoted context omitted.
To be fair, for aws that is hobbyist numbers. We (400 people data company) pay 10 times that amount. Let alone big enterprises. We do get discount, but it wont make it cheap.
There’s a lot of middleground between hobbyists and your company’s use ;) Most mid-sized publishers I’ve worked with are in the $4-10k/mo range depending on CDN availability
My point is that the parent I was replying to replied to “only hobbyists pay full price on aws”. The parent was expecting to get a discount on a 10k monthly bill. It is a lot of money, but not to AWS. You probably wont get (much) discount on 10k a month.
Earlier quoted context omitted.
Have you not seen some of the replies at the link? 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."
Why would a paying customer use the open source version? Deployment in non-prod?
Earlier quoted context omitted.
When you always published and built Docker images for the public you are creating an expectation, people will rely on that and will chose your software based on that expectation. 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 ab…
There is absolutely nothing malicious or suspicious about deciding not to provide docker images or binaries. Doing so does not hide or guard you against CVE's, which are entirely unrelated to such optional processes. 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…
so its a communications issue? if minio or whoever explains this, OK. that's not what happened, so it's not what happened.