Hi, Some weeks ago, I opened an issue to move our docker/container image to the wildfly organization in GitHub (instead of the current jboss-dockerfiles organization). This transfer of project would have no user impact (images will continue to be published on quay.io/wildfly/wildfly registry) but will simplify the maintenance of the project (with maintainers that are already in the wildfly organization). It will also simplify the integration of the image documentation on docs.wildfly.org. It will have a little impact on the GitHub actions quota but this is a low activity project with few PRs opened at any given time. One thing that will have to change is the name of the project (wildfly is already taken by WildFly :) The suggestion with the most votes is github.com/widfly/wildfly-container < http://github.com/widfly/wildfly-container>;. Again, this has no user impact on the name of the images published in Quay <http://quay.io/>;. I’m planning to do this move in a few weeks but I want to make sure that any questions/concerns can be addressed before we push the transfer button. If you have any feedback, please reply to the issue[1]. Thanks, Jeff [1] https://github.com/jboss-dockerfiles/wildfly/issues/234 -- Jeff Mesnil Engineer @ Red Hat http://jmesnil.net/ _______________________________________________ wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org Privacy Statement: https://www.redhat.com/en/about/privacy-policy List Archives: https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message...

On 14 Feb 2025, at 08:47, Jeff Mesnil <jmesnil(a)redhat.com&gt; wrote: Hi, I did not see any concerns or objections with that decision. So I’ll proceed with the transfer to a new github.com/widfly/wildfly-container <http://github.com/widfly/wildfly-container> repository. As a reminder, this will not have any user impact. Images will continues to be published to quay.io/wildfly/wildfly <http://quay.io/wildfly/wildfly>;. Best regards, jeff > On 13 Jan 2025, at 16:22, Brian Stansberry <brian.stansberry(a)redhat.com&gt; wrote: > > +1 > > On Mon, Jan 13, 2025 at 4:26 AM Jeff Mesnil <jmesnil(a)redhat.com <mailto:jmesnil@redhat.com>> wrote: >> Hi, >> >> Some weeks ago, I opened an issue to move our docker/container image to the wildfly organization in GitHub (instead of the current jboss-dockerfiles organization). >> >> This transfer of project would have no user impact (images will continue to be published on quay.io/wildfly/wildfly <http://quay.io/wildfly/wildfly> registry) but will simplify the maintenance of the project (with maintainers that are already in the wildfly organization). >> >> It will also simplify the integration of the image documentation on docs.wildfly.org <http://docs.wildfly.org/>;. >> >> It will have a little impact on the GitHub actions quota but this is a low activity project with few PRs opened at any given time. >> >> One thing that will have to change is the name of the project (wildfly is already taken by WildFly :) The suggestion with the most votes is github.com/widfly/wildfly-container <http://github.com/widfly/wildfly-container> <http://github.com/widfly/wildfly-container>;. Again, this has no user impact on the name of the images published in Quay <http://quay.io/>;. >> >> I’m planning to do this move in a few weeks but I want to make sure that any questions/concerns can be addressed before we push the transfer button. >> If you have any feedback, please reply to the issue[1]. >> >> Thanks, >> Jeff >> >> >> [1] https://github.com/jboss-dockerfiles/wildfly/issues/234 >> -- >> Jeff Mesnil >> Engineer @ Red Hat >> http://jmesnil.net/ >> _______________________________________________ >> wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org> >> To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org <mailto:wildfly-dev-leave@lists.jboss.org> >> Privacy Statement: https://www.redhat.com/en/about/privacy-policy >> List Archives: https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message... > > > > -- > Brian Stansberry > Principal Architect, Red Hat JBoss EAP > WildFly Project Lead > He/Him/His -- Jeff Mesnil Engineer @ Red Hat http://jmesnil.net/