In general, there is nothing that prevents this PMC to provide docker images (as of today).
There is no restriction from the ASF regarding the use of DockerHub, i.e. if this PMC decides to claim the official namespace (tomee) or distribute under apache/tomee on DockerHub it would be possible ;-) The official namespace has some goodies regarding build support. The latter a bit more control in terms of distribution and government. Regarding your question: don't know the reasoning, might be historical. DockerHub support or Docker in general is rather "new" in the ASF ;-) Gruß Richard Am 22. Dezember 2024 18:57:40 MEZ schrieb Rod Jenkins <r...@rodandmichelle.com>: >I could be wrong, but it was explained to be that Apache foundation is not >responsible for the official docker images. David could explain better. > >As far as the automation, this is something I’ve been wanting to work on, but >have not had the time. > >As far as other folks having write access to the repo, I’m not opposed as long >as the PRs can be reviewed. Again, TomiTribe would have to weigh in. > > >Rod. > >Sent from my iPhone > >> On Dec 22, 2024, at 10:20 AM, Markus Jung <ju...@apache.org> wrote: >> >> Hey all, >> >> just a quick question that has been popping up in my head over and over >> again over the last couple of months after basically every TomEE release: >> >> Why are the TomEE docker images held in a repository under the tomitribe >> organization? Is this just a historical thing, or is there more reasoning to >> it? This always slows us down pushing new releases to dockerhub because we >> need to wait for someone from tomitribe to merge new releases. Maybe we can >> improve that somehow by granting all TomEE committers write access to that >> repository? Or maybe even move it entirely into the hands of the ASF? >> >> >> Thanks >> >> Markus
