Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transition "composer/composer" Docker image on Docker Hub to Composer maintainers #5751

Closed
eugene-dounar opened this issue Oct 4, 2016 · 7 comments

Comments

@eugene-dounar
Copy link

Hi folks!
Some time ago I was added to maintainers of composer/composer image on Docker Hub. Few days ago I got an email from Docker about transition of this image to Composer maintainers.

As of my understanding image maintainers are ok with the transition. But as there are people using the image we need to work out some transition plan.

@alcohol
Copy link
Member

alcohol commented Oct 4, 2016

We do not plan on moving the source repository, nor will the existing image be ejected from the composer organization. It is purely an administrative change (ownership of the organization).

@pmoust
Copy link

pmoust commented Oct 4, 2016

that's good to know.

The number of pulls on the images under the dockerhub org suggests that if a transition is to take place it needs to be smooth or else it will break CI/dev workflows for a lot of people.

(Speaking as someone that is^H^Hwas one of the Docker Hub maintainers, as well as someone that relies on those images to perform CI builds).

@alcohol
Copy link
Member

alcohol commented Oct 4, 2016

The only changes I would like to implement asap is setting up some webhooks so that builds for the 'latest' tags are triggered whenever we merge changes into the master and/or 1.2 branch. Cause I noticed that the latest tags are lagging behind rather significantly.

@stof
Copy link
Contributor

stof commented Oct 4, 2016

Well, it would make sense to move the source repository to the github organization, if we can update the docker hub to look for automated builds in the new repo. This should not require changing the image name in the hub (unless the docker community decided not to support updating the location of the source repo)

@alcohol
Copy link
Member

alcohol commented Oct 4, 2016

I know Seldaek is a bit reluctant regarding moving the Github repository into the Composer organization. I'm neutral, though I personally think it could benefit from the move (increased visibility perhaps/hopefully could lead to more contributors?). It would require some planning though, but it's a fairly simple process.

@pmoust
Copy link

pmoust commented Oct 4, 2016

A webhook triggered per push event can be easily added and is much needed.
👍

@Seldaek
Copy link
Member

Seldaek commented Oct 12, 2016

Done here I believe?

@Seldaek Seldaek closed this as completed Oct 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants