Skip to content

README: clarify who maintains the image #46

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

Merged
merged 1 commit into from
Oct 12, 2015
Merged

README: clarify who maintains the image #46

merged 1 commit into from
Oct 12, 2015

Conversation

michaelklishin
Copy link
Collaborator

We've seen some folks interpret "official image" as "maintained by the RabbitMQ team", so perhaps it's worth clarifying.

We've seen some folks interpret "official image" as "maintained by the RabbitMQ team", so perhaps it's worth clarifying.
@yosifkit
Copy link
Member

That seems fine to me.

On a related note, we are open to having upstreams maintain their own image if they would like (https://github.com/docker-library/official-images#maintainership). Since the first step is getting involved, we've already seen your team jump in on several issues and even add fixes upstream 😄. Once the repo is transferred, it is just a PR to docker-library/official-images to update the commit referencces and then a PR when necessary to update the Docker Hub docs through docker-library/docs. But if you guys would rather that we keep maintaining it, that is fine too.

@tianon
Copy link
Member

tianon commented Oct 12, 2015 via email

tianon added a commit that referenced this pull request Oct 12, 2015
README: clarify who maintains the image
@tianon tianon merged commit ec0a0c9 into docker-library:master Oct 12, 2015
@michaelklishin
Copy link
Collaborator Author

You have been doing a great job with this image — I see no reason for us to try to get more involved :)

@tianon
Copy link
Member

tianon commented Oct 12, 2015 via email

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

Successfully merging this pull request may close these issues.

3 participants