Move the project to the wildfly organization?

[jmesnil]

This project is independent of other projects in jboss-dockerfiles and is now maintained by the WildFly team.

I think we should move it to the wildfly organization to make it closer to the main WildFly codebase. It would also help collaboration, maintenance and integration between projects by having them in the same GitHub organization.

We would have to rename this project though (as https://github.com/wildfly/wildfly is already taken for the app server codebase).
Suggestions would be:

• github.com/widfly/wildfly-docker
• github.com/widfly/wildfly-container

[goldmann]

The second option for the repository name is much better IMHO.

[jamezp]

I also agree with the second option or potentially a more verbose wildfly-open-container. No strong opinion either way though. I just feel the term "container" has become very overloaded and sometimes verbosity helps :)

[bstansberry]

Is there any kind of generic term for these kinds of images, that doesn't subsume our OpenShift images? Just 'container' plainly does.

Here we are, facing the hardest problem in software engineering.

[jamezp]

The only reason I suggested "open-containers" was because of https://opencontainers.org/ which Docker, podman and OpenShift can all use.

[jmesnil]

This project has been transferred to https://github.com/wildfly/wildfly-container. GitHub automatically redirects the link from github.com/jbossdocker-files/wildfly to this new repo.