Namespacing of subproject Docker images vs. Incubator policy

2016-08-28 Thread Mike Jumper
Hello all, We, Apache Guacamole (incubating), would like to migrate our project's Docker images to something beneath the ASF, but I am unsure how to proceed, nor the form that this migration would best take. We currently have two repositories which provide Docker images: incubator-guacamole-clien

Re: Namespacing of subproject Docker images vs. Incubator policy

2016-08-28 Thread Roman Shaposhnik
First of all, the way apache org is setup on GitHub make me 99% sure that the only artifacts allowed there would be release ones. If we agree on that, I see no problem with apache/incubator-foo naming of your *released* Docker images. Note that there was a separate discussion focused on where

Re: Namespacing of subproject Docker images vs. Incubator policy

2016-08-28 Thread John D. Ament
On Sun, Aug 28, 2016 at 8:58 PM Roman Shaposhnik wrote: > First of all, the way apache org is setup on GitHub make me 99% sure > that the only artifacts allowed there would be release ones. > > If we agree on that, I see no problem with >apache/incubator-foo > naming of your *released* Docker

Re: Namespacing of subproject Docker images vs. Incubator policy

2016-08-28 Thread Mike Jumper
On Aug 28, 2016 5:58 PM, "Roman Shaposhnik" wrote: > > First of all, the way apache org is setup on GitHub make me 99% sure > that the only artifacts allowed there would be release ones. > > If we agree on that, I see no problem with >apache/incubator-foo > naming of your *released* Docker ima

Re: Namespacing of subproject Docker images vs. Incubator policy

2016-08-28 Thread Mike Jumper
On Sun, Aug 28, 2016 at 6:49 PM, Mike Jumper wrote: > On Aug 28, 2016 5:58 PM, "Roman Shaposhnik" wrote: >> >> First of all, the way apache org is setup on GitHub make me 99% sure >> that the only artifacts allowed there would be release ones. >> >> If we agree on that, I see no problem with >>