Docker Community Forums

Share and learn in the Docker community.

Who or what process determines the owner of top-level repos?


(Mischief) #1

i’m curious who or what chooses the docker repos that get top-level names (i believe these are actually library/name under the hood).

what raised my curiosity is seeing a google/golang repo. i noticed there’s also just ‘golang’ repo, apparently sponsored by stackbrew. why should stackbrew get the ‘golang’ name when google is in fact the creator of the go language?


(Sam Saffron) #2

Yeah I was wondering that to, is there some sort of official process for this @sven ?


(Sven Dowideit) #3

The top level repositories actually have an implicit empty “” top-level
name. () or “_”

But I’m not sure how the they impact on organisation and user names.

I have found https://registry.hub.docker.com/repos/hylang/ - a user with
the same name as a top level image https://registry.hub.docker.com/_/hylang/

I’d say that the ‘golang’ image is something the Docker project, via the
stackbrew repo and its contributors as committed to keeping up to date,
whereas google/* are images that google will make their own decisions on.

@tianon ?


(Tianon Gravi) #4

See https://github.com/docker/stackbrew for the process by which official images are made and maintained. The reason we made our own “golang” image is that the only person we could get interested in doing such a thing from Google was proppy, but he was too busy with other stuff to respond and actively maintain such a thing. We’re definitely not opposed to Google taking it over, as long as they actually actively maintain it.

For example, the CentOS Rel-Eng team maintains the official “centos” images now, and we’ve got an active upstream Perl contributor maintaining the “perl” images, which is also cool. I think it’s important to note that we’re not trying to step on anyone’s toes - we need quality content, no matter who maintains it, and we’re not opposed to turning that burden onto upstream if they can maintain.


(Mischief) #5

thank you for the responses. i actually have my own golang repo, but after seing ‘golang’ and ‘google/golang’, i might switch.

its sad to hear that maintainers could not be found from google, ill raise an issue on on the go mailing list to see if an official maintainer will appear.

thanks!


(Sven Dowideit) #6

The top level repositories actually have an implicit empty “” top-level
name. () or “_”

But I’m not sure how the they impact on organisation and user names.

I have found https://registry.hub.docker.com/repos/hylang/ - a user with
the same name as a top level image https://registry.hub.docker.com/_/hylang/

I’d say that the ‘golang’ image is something the Docker project, via the
stackbrew repo and its contributors as committed to keeping up to date,
whereas google/* are images that google will make their own decisions on.

@tianon ?


(Tianon Gravi) #7

I think that’s an accurate summary. We also have @proppy from Google collaborating on the golang images now.


(Sven Dowideit) #8

The top level repositories actually have an implicit empty “” top-level
name. () or “_”

But I’m not sure how the they impact on organisation and user names.

I have found https://registry.hub.docker.com/repos/hylang/ - a user with
the same name as a top level image https://registry.hub.docker.com/_/hylang/

I’d say that the ‘golang’ image is something the Docker project, via the
stackbrew repo and its contributors as committed to keeping up to date,
whereas google/* are images that google will make their own decisions on.

@tianon ?