検索

返信元:

But since the project is a container image, most people don't visit a website or repo after they've implemented the container, so there's a pretty solid chance that posting a statement of "Hey, we're going to retire this thing - use this thing instead" isn't going to be seen and current end-users will end up sticking with a stale, unmaintained version that isn't good for them and doesn't reflect well on us, either. It also doesn't seem great to up and delete it and break stuff for others.
返信 1 · Renote 0
This all makes it so much easier to understand why #DockerHub is littered with massive numbers of stale, insecure images and other than maybe making analytics available to everyone, I don't see any obvious way for how #Docker could make this better without being massively disruptive.
返信 1 · Renote 0

返信元:

I have an interesting problem at work. We aren't using one of our #opensource projects any more, but metrics seem to indicate that others are. But since we don't track end users in any way whatsoever, we have no way of reaching out to whoever they are to see how disruptive it would be for us to pull the plug or even if it's used within our own org! It's not much overhead to keep going at this point, but it's not zero.
返信 1 · Renote 0
One interesting point here is that #DockerHub doesn't give you pull analytics with regular paid tiers (there are two special programs that get it). You can query current amount of pulls with an API call, but if you haven't been doing that all along because you didn't know you needed that, then you don't get that info, so I can see it has a high number of pulls and the last time it was pulled, but I don't know how many unique IPs or regularity. #Docker #opensource
返信 1 · Renote 0