←back to thread

The Deletion of Docker.io/Bitnami

(community.broadcom.com)
329 points zdkaster | 1 comments | | HN request time: 0s | source
Show context
asmor ◴[] No.45049447[source]
> However, in order to sustain and support the dedicated team of engineers who maintain and build new charts and images, a subscription will be required if an organization needs the images and charts built and hosted in an OCI registry for them.

This is such a naive take. Bitnami images were a sign of goodwill, a foot in the door at places were the hardened images were actually needed. They just couldn't compete with the better options on the market. This isn't a way to fix it, it's extortion. This is the same thing Terraform Cloud did, and I don't think that product is doing so hot.

> Essentially, Bitnami has been the Jenkins of the internet for many years, but this has become unsustainable.

It's other people's software, so it's very rich of Bitnami to accuse anyone of freeloading when their only contribution is adding config options to software that maybe corresponds to a level 2 on the OperatorFramework capability scale[1] - usually more of a 1.

[1]: https://operatorframework.io/operator-capabilities/

replies(11): >>45050005 #>>45050042 #>>45050416 #>>45050488 #>>45050688 #>>45050800 #>>45051410 #>>45052041 #>>45053279 #>>45054090 #>>45055791 #
darkwater ◴[] No.45050416[source]
> It's other people's software, so it's very rich of Bitnami to accuse anyone of freeloading when their only contribution is adding config options to software

I'm not going to defend a corporation but this sentence feels very entitled. They were providing it for free, you could use it. They are not going to provide it for free anymore, you migrate to something else or self-maintain it and say "thank you for the base work you did I can use now"

replies(4): >>45050558 #>>45050612 #>>45051344 #>>45053846 #
throw__away7391 ◴[] No.45050558[source]
When a project is abandoned, when updates are slow, when features people want are not being released, when tracking upstream dependency updates are delayed, sure, you are not entitled to anything and I’ll be the first one to say get off your butt and contribute. In the other hand when you engage with the community for years under an OSS/free context then once the community has invested in your project, learning it, creating learning resources for it, integrating it into their own projects, and you never communicated your intention to “wait until it gets big then then pull the rug” it feels like a disingenuous bait and switch. The reason it feels that way is because it is a disingenuous bait and switch. This is even more so the case when you built your project on top of other projects.

I have no problem using a paid product or service or paying for support on a OSS product, but will never pay one of these bait and switch scams a dime, no matter how much engineering effort it takes.

replies(2): >>45051513 #>>45054643 #
1. darkwater ◴[] No.45051513[source]
I understand the sentiment and where it comes from, and I'm not saying it's a good decision from Broadcom (I think it is a bad one indeed!). But still, this risk is part of the game. Even if it was full opensource and with a broad community, it was still a single vendor, not even a non-profit umbrella like the Apache or Linux Foundation. So, the risk of trusting a single vendor was there.

The good thing of it being opensource is that someone else (company, community, foundation or whatever) can step in, fork it, and maintain it from now on, unlike what happens with proprietary software or SaaS.