On Sun, Apr 26, 2015 at 7:27 AM, Colin Walters <walters(a)verbum.org> wrote:
On Sat, Apr 25, 2015, at 12:16 PM, Dennis Gilmore wrote:
>
https://fedoraproject.org/wiki/User:Adamwill/Draft_fedora_image_naming_po...
These aren't image names so much as they're *namespace prefixes*. The
ref prefix is strongly analogous to the `fedora/` prefix on the Docker Hub
for the base image.
If the Docker image were changed to be a product
of the Cloud group, and we changed the Docker name to be:
`Fedora-Cloud_Docker` or something, it would *really* stick out as
strange on the Hub.
Many things use what Sourceforge calls "unix names" style:
http://sourceforge.net/p/forge/documentation/Renaming/
such as package names, yum repository IDs, usernames,
Docker image names, etc. etc. The OSTree "osname" is
intended to be in this style.
Given that it's a namespace, the simplest would just be `fedora`,
like the Docker image name. But failing that, the current
`fedora-atomic` is very much preferable over introducing
a "product naming style" where "unix names" are expected.
Does that explain things better? Thanks!
For what it's worth I think this makes sense. By framing ostree naming
as something analogous to yum repositories or docker hub registry
entries I think it makes sense to follow the "unix names" style in
some respect. What this will look like within the release tooling, I
don't know the details of just yet, but I think from an user
perspective the name change is a logical choice.
-AdamM
_______________________________________________
rel-eng mailing list
rel-eng(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/rel-eng