[atomic-wg] Issue #202 `Syncing released Fedora container images to Docker Hub`

2017-02-15 Thread Dusty Mabe
dustymabe added a new comment to an issue you are following: `` seems like enough people are +1. Closing this "question". `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/202 ___ cloud mailing list --

[atomic-wg] Issue #202 `Syncing released Fedora container images to Docker Hub`

2017-02-08 Thread Kushal Das
kushal added a new comment to an issue you are following: `` +1 to stay with the current namespace. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/202 ___ cloud mailing list --

[atomic-wg] Issue #202 `Syncing released Fedora container images to Docker Hub`

2017-02-08 Thread Dusty Mabe
dustymabe added a new comment to an issue you are following: `` +1 for current name space `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/202 ___ cloud mailing list -- cloud@lists.fedoraproject.org To

[atomic-wg] Issue #202 `Syncing released Fedora container images to Docker Hub`

2017-02-08 Thread Trishna Guha
trishnag added a new comment to an issue you are following: `` +1 on sticking with the current namespace. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/202 ___ cloud mailing list --

[atomic-wg] Issue #202 `Syncing released Fedora container images to Docker Hub`

2017-02-07 Thread Adam Miller
maxamillion reported a new issue against the project: `atomic-wg` that you are following: `` Currently the plan is to sync all container images from Fedora's Registry to the Docker Hub. Do we want to do this under the current [fedora namespace](https://hub.docker.com/u/fedora/) or create a new