On Sun, Aug 28, 2016 at 8:58 PM Roman Shaposhnik <ro...@shaposhnik.org>
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 images.
>
There is from an eventually a TLP stand point. apache/guacd and
apache/incubator-guacd are not the same. I wouldn't be able to migrate an
instance from one to the other. I'd actually recommend the incubating part
in the version #, similar to what we do for most other artifacts, so that
it becomes apache/guacd/1.0.0-incubating
>
> Note that there was a separate discussion focused on where is the right
> place for nightly/snapshot Docker builds to be deposited to.
>
> Sadly, that discussion bore no fruit :-(
>
Was there? I would love to get discussing about that. Not for an
incubating project but for a TLP. I share concerns about "latest" but
also see benefit to developers being able to use a "LATEST" tagged
pre-release.
>
> Thanks,
> Roman.
>
> On Sun, Aug 28, 2016 at 4:21 PM, Mike Jumper <mike.jum...@guac-dev.org>
> wrote:
> > 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-client [1] and incubator-guacamole-server [2].
> > Prior to acceptance into the Apache Incubator, these repositories were
> > used to produce the "glyptodon/guacamole" [3] and "glyptodon/guacd"
> > [4] images respectively.
> >
> > As there is already an "apache/*" organization defined at Docker Hub
> > (albeit a virtual desert) [5] and there was positive discussion
> > regarding including the images of incubating projects under that
> > organization [6], it seems that would be the logical and
> > straightforward choice ... but because one of those images ("guacd")
> > would not be namespaced by the project's own name, I'm unsure if this
> > is actually possible/allowed.
> >
> > Ideally we would end up with a mapping like:
> >
> > incubator-guacamole-client -> apache/guacamole
> > incubator-guacamole-server -> apache/guacd
> >
> > Or, since we're incubating, perhaps:
> >
> > incubator-guacamole-client -> apache/incubator-guacamole
> > incubator-guacamole-server -> apache/incubator-guacd
> >
> > But again, I'm not sure if "apache/incubator-guacd" would be a
> > violation of policy.
> >
> > Alternatively, a cleaner approach could be to define a Docker Hub
> > organization specific to the project, as that would provide a nice
> > analogy to the project/subproject relationship that exists between
> > Apache Guacamole the "guacamole" and "guacd" applications:
> >
> > incubator-guacamole-client -> guacamole/guacamole
> > incubator-guacamole-server -> guacamole/guacd
> >
> > But I'm not sure if THAT would be a violation of policy. Further,
> > after creating exactly such an organization for the sake of testing,
> > I've found that I can't set up the necessary linkage for enabling
> > automatic builds (the organization would need to be owned by a user
> > with sufficient access rights to the Apache GitHub mirrors).
> >
> > Any suggestions?
> >
> > Thanks,
> >
> > - Mike
> >
> > [1] https://github.com/apache/incubator-guacamole-client
> > [2] https://github.com/apache/incubator-guacamole-server
> > [3] https://hub.docker.com/r/glyptodon/guacamole/
> > [4] https://hub.docker.com/r/glyptodon/guacd/
> > [5] https://hub.docker.com/r/apache/
> > [6]
> http://mail-archives.apache.org/mod_mbox/incubator-general/201604.mbox/%3CCANyrgvfAWifLkkvAccAV22Q9uyo8g3so=BJ0JFZ8oV16Bt=k...@mail.gmail.com%3E
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
