<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>terom</author><text>If you are deleting the organizational data and effectively archiving [1] all the images, keeping only the option for public images to be pulled but not updated... then how will affected maintainers be able to delete their now out of date public images after the 30 day cut-off? You will have to retain enough of the organization data to allow that to happen.&lt;p&gt;Keeping the public images available in an archived state is okay for specific image references, but questionable for specific image tags and somewhat irresponsible for the `latest` tag. A `latest` tag that cannot be updated is ... worse than no `latest` tag.&lt;p&gt;Responsible maintainers that are unable to apply for open-source status or otherwise sponsor their usage of organization public repos should be advised to delete their public repos.&lt;p&gt;Responsible users of public images on Docker Hub need to have a way to determine which images will be affected, and which will continue to be maintained. Archiving the public repos gives an extended grace period, but users will still need to be prepared to notice if they end up using a now unmaintained, archived repo and migrate to alternative image sources.&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=35188691&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=35188691&lt;/a&gt;</text><parent_chain><item><author>mikesir87</author><text>(from Docker DevRel team)&lt;p&gt;&amp;gt; Given these statements directly contradict each other&lt;p&gt;Actually... they aren&amp;#x27;t contradictory. The organization data will be retained for 30 days and is subject to deletion. That data includes the teams, memberships, etc. But, it wasn&amp;#x27;t clear what we were going to do about the images. Keeping the public images is important as many other images build on top of them.&lt;p&gt;&amp;gt; It feels like they changed the actual strategy&lt;p&gt;We recognize it might feel that way, so apologies. But, that&amp;#x27;s part of where we are recognize it wasn&amp;#x27;t clear the technical details... we didn&amp;#x27;t talk at all about the images. After the feedback, we recognized this, so wanted to make that clear.</text></item><item><author>nielsole</author><text>Previous communication:&lt;p&gt;&amp;gt; If you don&amp;#x27;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.&lt;p&gt;New communication:&lt;p&gt;&amp;gt; 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 communications failed to make this clear.&lt;p&gt;Given these statements directly contradict each other I am a bit surprised this is called clarification. It feels like they changed the actual strategy, not just the communication around it.</text></item></parent_chain></comment><story><title>We apologize. We did a terrible job announcing the end of Docker Free Teams</title><url>https://www.docker.com/blog/we-apologize-we-did-a-terrible-job-announcing-the-end-of-docker-free-teams/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>vertis</author><text>Deleting &amp;#x27;organization data&amp;#x27; absolutely read that they would delete everything. Changing direction and back pedaling with a non-apology is borderline insulting.&lt;p&gt;I understand the need to make money as a company, but it really is biting the hand that fed messing with open source maintainers</text><parent_chain><item><author>mikesir87</author><text>(from Docker DevRel team)&lt;p&gt;&amp;gt; Given these statements directly contradict each other&lt;p&gt;Actually... they aren&amp;#x27;t contradictory. The organization data will be retained for 30 days and is subject to deletion. That data includes the teams, memberships, etc. But, it wasn&amp;#x27;t clear what we were going to do about the images. Keeping the public images is important as many other images build on top of them.&lt;p&gt;&amp;gt; It feels like they changed the actual strategy&lt;p&gt;We recognize it might feel that way, so apologies. But, that&amp;#x27;s part of where we are recognize it wasn&amp;#x27;t clear the technical details... we didn&amp;#x27;t talk at all about the images. After the feedback, we recognized this, so wanted to make that clear.</text></item><item><author>nielsole</author><text>Previous communication:&lt;p&gt;&amp;gt; If you don&amp;#x27;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.&lt;p&gt;New communication:&lt;p&gt;&amp;gt; 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 communications failed to make this clear.&lt;p&gt;Given these statements directly contradict each other I am a bit surprised this is called clarification. It feels like they changed the actual strategy, not just the communication around it.</text></item></parent_chain></comment><story><title>We apologize. We did a terrible job announcing the end of Docker Free Teams</title><url>https://www.docker.com/blog/we-apologize-we-did-a-terrible-job-announcing-the-end-of-docker-free-teams/</url></story>