Most active commenters
  • ianbutler(5)

←back to thread

170 points nimbius | 13 comments | | HN request time: 0.001s | source | bottom
Show context
stronglikedan ◴[] No.45684922[source]
I feel sorry for the OMIO maintainer community considering how entitled the MinIO community revealed themselves to be.
replies(1): >>45685046 #
1. Spivak ◴[] No.45685046[source]
Step 1: I made this thing and am freely giving it away for the benefit of everyone. Come join the party!

Step 2: Wow, because this is a community project I can depend on it continuing to exist freely thanks to a large base of diverse parties invested in its continued growth and availability.

Step 3: Just kidding, I'm taking back the thing I made. Sorry if you were depending on it, migrate to something else or pay me.

Step 4: WTF dude?!

Step 5: Why are you all so entitled?

replies(2): >>45685256 #>>45685294 #
2. michaelgiba ◴[] No.45685256[source]
They stopped publishing images, not like they changed anything significant about the product itself.

Frankly the whole thing is not newsworthy

replies(2): >>45685624 #>>45686276 #
3. ianbutler ◴[] No.45685294[source]
What is so hard about the idea that you are not perpetually entitled to the free labor of other people?

The only thing they owed people here was a 60 day notice imo. That would better respect the social contract.

replies(3): >>45685399 #>>45685455 #>>45685730 #
4. Spivak ◴[] No.45685399[source]
I'm not. If they had simply said, "Hey this is getting to be too much work and I don't want to continue anymore. Let me know if you're interested in taking over maintainership of the project." then that's fine. Hell even if they just archived the project and ghosted never to be seen again that's also fine.

It's (yet another) example of a company donning the trappings of an open source project as a "growth hack" or to secure VC funding and then rug pulling when they decide they want to try and squeeze their user base for cash. They're the corporate stooges that insert themselves into high-trust communities and subcultures to make a buck and ruin it for everyone.

replies(1): >>45685728 #
5. ekjhgkejhgk ◴[] No.45685455[source]
I agree with you. But people are allowed to complain, so they're complaining. And the maintainers are allowed to ignore the complaining. Everything is according to the process.
replies(1): >>45685753 #
6. JokerDan ◴[] No.45685624[source]
> not like they changed anything significant about the product itself

They had already done this months ago, they changed the licence and stripped a lot of the code of their admin UI/object browser. So a lot of the features vanished for people overnight if they updated. This is what the OP is linked to - a fork at the point that they did this. This was work already done, feature already widely in use, they decided to take it out of what was available to the community.

So the product has significantly changed and offering had been reduced. That in addition to the stopping of publishing images - both without notice - caused a decent bit off community 'wtf'.

7. ianbutler ◴[] No.45685728{3}[source]
I mean is it though? They've been open source for over a decade thats a really long con I guess.

It’s more likely circumstances have changed. Which is why forking is a thing and you dont have to be oss forever.

I stand by my assertion that this would have been fine if they didn’t communicate like garbage. They should have said what you said and gave a good off ramp period.

8. evilduck ◴[] No.45685730[source]
There was a 60 days notice? https://blog.min.io/

The only notice I have received is from the blowback of their behavior. Walking away from supporting the open source product at any other time than in the wake of a security vulnerability disclosure would have been received better. Sure they're not legally culpable for fixing anything but they're now obviously untrustworthy as a business partner going forwards.

replies(1): >>45685851 #
9. ianbutler ◴[] No.45685753{3}[source]
Yeah I suppose you’re right
10. ianbutler ◴[] No.45685851{3}[source]
Oh then like I don’t even see the problem. That said I think like a direct notification through email or something is probably better than random blog post, but I digress:

They planned to walk away earlier as I believe I saw its really just unfortunate timing.

If you’re doing business with them you should be on a business license with a contract and legal guarantees. I understand it sucks, but it’s a little bit of a self own imo if you’re only on their oss for business purposes. That also kind of breaks the social contract in the opposite direction imo.

replies(1): >>45686251 #
11. 0x457 ◴[] No.45686251{4}[source]
> Oh then like I don’t even see the problem. That said I think like a direct notification through email or something is probably better than random blog post, but I digress:

How would they know your email if you are using minio-oss? Blog post is for sure enough. Decision itself is dumb, it's a public repo with free runners to build images that downloaded 10M times. That behavior is much different how you had to go somewhere else to get OpenJDK binaries.

Maintaining existing build pipeline is nearly zero cost.

replies(1): >>45686921 #
12. 0x457 ◴[] No.45686276[source]
https://github.com/minio/object-browser/issues/3546
13. ianbutler ◴[] No.45686921{5}[source]
Doesn’t matter it’s not your call.

People should begin to think about these externalities. I do.

If you’re using them for business you should probably have a more formal arrangement where they could email you.