How difficult would it be to use simply glassfish as the image name? The reason is that as you know, GlassFish is still better understood (and perhaps easier to understand) than Eclipse GlassFish. I imagine Jetty
had the same issue and it seems they have sorted it out in Docker Hub.
Hi David,
Looks like you have done some good work there and I think it would be a good thing to have an Eclipse GlassFish docker image.
I also agree that to follow the Eclipse Development Process the source code of any image must be in a GlassFish project repository. The Project Handbook has guidance on
External Resources see Eclipse Project Handbook | The Eclipse Foundation and for Docker Hub specifically
Eclipse Project Handbook | The Eclipse Foundation. As long as the guidelines are followed RE: Docker Hub I support moving the source into the project and hosting the image on Docker
Hub. Reading the guidelines having a dockerhub name that is not eclipseglassfish or some variant of requires PMC and/or PMO approval.
Thanks
Steve
Hi GlassFish developers!
OmniFish did some efforts for the official Eclipse GlassFish Docker Image, however things are not so simple as we would wish. To make everything correct I have created the issue on GitLab:
https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/3138
I would like to know your opinion, especially
- if you would like to use the official Eclipse GlassFish Docker Image
- if you would like to contribute to the official Eclipse GlassFish Docker Image
- if you have any thoughts about it
I look forward to your responses and have a nice Friday!
--
David Matejcek | OmniFish
david.matejcek@xxxxxxxxxxx