Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

We apologize. We did a terrible job announcing the end of Docker Free Teams

docker.com

Post reply on HN
Print view View original

61–70 of 334 posts

Re: We apologize. We did a terrible job announcing the end of Docker Free Teams

#61

Post by dheera »

system16 wrote: post #16

It's almost becoming a cliche for companies to release damage control follow-ups like this after they pull a bait and switch. It's always "we're sorry that we didn't communicate our bait and switch effectively". Not we're sorry that we pulled a bait and switch. We're sorry you didn't understand the value in this bait and switch. It's your fault, actually. But we're sorry you're angry. Now stop giving us negative atte…

The forces of capitalism reward this, it will continue to happen as long as we pick pure capitalism as a system, and keep assigning values to companies purely on financials with no consideration toward their ability to empathize and communicate.

Re: We apologize. We did a terrible job announcing the end of Docker Free Teams

#62

Post by ryan29 »

Edit: It looks like you can migrate from a team to a personal account:

> You can migrate from a Free Team organization to a Personal account by opening a support ticket. No action will be taken against your account while your ticket is being processed.

Re: We apologize. We did a terrible job announcing the end of Docker Free Teams

#63

Post by ignoramous »

> ...we recently emailed accounts that are members of Free Team organizations, to let them know that they will lose features unless they move to one of our supported free or paid offerings. This impacted less than 2% of our users.

What percentage of those orgs / users hosted popular docker images? Surely, 2% is a small enough number to warrant a public apology?

Re: We apologize. We did a terrible job announcing the end of Docker Free Teams

#64

Post by sleepytimetea »

nielsole wrote: post #56

Previous communication: > If you don't upgrade to a paid subscription, Docker will retain your organization data for 30 days, after which it will be subject to deletion. During that period you will maintain access to any of your public images. New communication: > We’d also like to clarify that public images will only be removed from Docker Hub if their maintainer decides to delete them. We’re sorry that our initial…

Exactly ! I remember the original email mentioned deletion and now they say "we never said that".

Time to get rid of Docker in our world.

Re: We apologize. We did a terrible job announcing the end of Docker Free Teams

#65

Post by pnw »

InvaderFizz wrote: post #47
pnw wrote: post #27

Earlier quoted context omitted.

I get invoices for my $5 Pro plan. Do you mean they wouldn't take the order on credit?

Probably means they would not do NET30 or the like terms to fit with their corporate purchasing workflow.

Pretty hard to get NET30 invoicing on a transaction which is less than $450, especially if you've chosen the monthly plan. It's just not worth the labor chasing an unpaid $450 invoice every damn month.

Re: We apologize. We did a terrible job announcing the end of Docker Free Teams

#66

Post by dheera »

afarrell wrote: post #6
mellowyeller wrote: post #3

The third sentence in their apology is "This impacted less than 2% of our users." What is that supposed to convey? It feels like a handwave. 'We're sorry we mistreated you, look how small you are to us.'

One of the difficulties of public relations is communicating to multiple audiences at once. One of Docker’s audiences are the paying customers who outside that 2% and would want some assurance that if docker makes errors, those errors are smaller in magnitude. This statement seems like it is aimed at assuaging the worries of that audience. Is it good practice? I do not know.

> One of the difficulties of public relations is communicating to multiple audiences at once.

Why not just release multiple statements and links?

"Click here for customized PR statement if you are a open source developer"

"Click here for customized PR statement if you are a closed source developer"

"Click here for customized PR statement if you are an executive who can't code"

"Click here for customized PR statement if you are a billionaire who invested in Docker but secretly don't know what it is"

etc.

Re: We apologize. We did a terrible job announcing the end of Docker Free Teams

#67

Post by linuxftw »

Lots of people outraged here, but did any organization step up to fill this (perceived) gap?

Docker is way too generous IMO. Petabytes of freeloader data they'll never generate a nickle from. Everyone around here wants people to pay $20/month for some newspaper, and spend $0/month on infrastructure that helps run the internet. It's crazy town.

Re: We apologize. We did a terrible job announcing the end of Docker Free Teams

#68

Post by renewiltord »

ericb wrote: post #25
eyeareque wrote: post #17

I’m guessing they did this change because the cost of giving a free service isn’t cheap for docker?

It seems the concept of a loss leader is "lost" on Docker. Some MBA with a spreadsheet at Docker hasn't realized that where the upstream OSS goes, the rest follow.

They've historically had trouble having that loss leader lead to a non-loss.

Re: We apologize. We did a terrible job announcing the end of Docker Free Teams

#69

Post by antoineMoPa »

chillbill wrote: post #29

What I’d like to know is why the hell is there so many Docker editions/licenses? Did docker just hire people who made Windows vista? Also, just switch to Podman already people…

Doesn't podman use docker.io images by default?

Re: We apologize. We did a terrible job announcing the end of Docker Free Teams

#70

Post by imron »

ryan29 wrote: post #62

Edit: It looks like you can migrate from a team to a personal account: > You can migrate from a Free Team organization to a Personal account by opening a support ticket. No action will be taken against your account while your ticket is being processed.

> I don't get it. It's still exactly the same problem for me.

So you do get it then.

Sorry, not sorry.

Post reply on HN