DX/Marketing issue with current README on hub.docker.com for 'plone' images

[fredvd]

I did a talk this week at the German Plone Symposium 'Plone-Tagung' and I got a question from someone why the ADDONS doesn't work.

Only then I realised that for Plone 6 in the documentation we are now referring to our 'second' generation of plone-backend and plone-frontend images, but if you search for plone on hub.docker.com the 'plone' image is shown first, and when you click on it, you get an explanation about Plone 5(.2) , being based on universal installer, etc. etc. : https://hub.docker.com/_/plone

This page is different from the 'plone' image under Plone: https://hub.docker.com/r/plone/plone. This page has some disclaimers about not using it in production, etc. etc. But the 'organisation' entry page on doesn't have this info. I'd very much like to make https://hub.docker.com/_/plone more generic, describe our 1st and 2nd 'generation' of images and point visitors to docs.plone.org.

I've browsed the settings on hub.docker.com but I have no idea where this generic page is coming from or how I can update it. I suspect it is a setting where an image README is promoted to the organisation, but I haven't found it yet.

So first question is: how can we edit this? Second quetions, but for a new ticket or a branch hopefulley, would be to prepare, edit and publish a new more generic landing page for the plone project.

[mauritsvanrees]

It comes from here: https://github.com/plone/plone.docker

[mauritsvanrees]

O, sorry, that is the repo where you opened this issue. :-D

[mauritsvanrees]

I think the content comes from here: https://github.com/docker-library/docs/tree/master/plone

The PR 8 years ago that added Plone there, is this one: https://github.com/docker-library/docs/pull/484/files

[avoinea]

@fredvd @mauritsvanrees https://github.com/docker-library/official-images and https://github.com/docker-library/docs/tree/master/plone

You'll need to do a fork and PR on these repos.

See for example: https://github.com/docker-library/docs/pulls?q=is%3Apr+is%3Aclosed+Plone

[stevepiercy]

There's an open PR to resolve this issue https://github.com/docker-library/docs/pull/2479.

[stevepiercy]

After that PR is merged, there are still a couple more tasks to perform. We need to promote plone-backend and plone-frontend as official Docker images. That includes merging the docs files from https://github.com/docker-library/docs/pull/2479 to be compliant with official images docs. Documentation of the process is at https://github.com/docker-library/docs?tab=readme-ov-file#how-do-i-add-a-new-images-docs.

• [ ] Remove deprecation notice from https://github.com/docker-library/docs/pull/2479, and reword content.md accordingly.
• [ ] Revise tags in https://github.com/docker-library/official-images/blob/master/library/plone
• [ ] Revise README.md for https://github.com/plone/plone-frontend/.
• [ ] Revise README.md for https://github.com/plone/plone-backend/.
• Update Plone 6 Documentation.
  • [ ] Find and replace docker run -p 8080:8080 plone/plone-backend:6.0 start with docker run -p 8080:8080 plone:backend-6.0 start.
  • [ ] Other?

[stevepiercy]

For anyone following this issue, please join the lively discussion in Discord at https://discord.com/channels/786421998426521600/787390558809096192.