-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Refactor the way information (especially links) are presented #888
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
Conversation
|
@Djelibeybi I think the Supported tags and respective
|
|
Oh shoot, |
|
(OK, comment above updated with the adjusted content.) |
|
@tianon looks 👍 to me. Nice work. |
|
Thanks @Djelibeybi ❤️ -- it's been a lot of work today to track down and corroborate all this information 😅, but I think it'll really be helpful to our users (and upstreams who aren't maintaining their associated image) |
This should make it much faster to find the right place to file issues, get help, find out whether upstream maintains an image, etc. I've done my best to represent each `REPO/maintainer.md` file appropriately, but I might have missed some (or there might be something else a maintainer prefers be listed there, either more or less descriptive, for example), which would be welcome contributions following this change.
|
@mlhess @CashWilliams how's this? ❤️ (this is the change I mentioned over in #886 (comment)) Quick reference
|
yosifkit
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great to me. If any maintainer wishes to adjust their group name, PRs to change are always welcome.

This should make it much faster to find the right place to file issues, get help, find out whether upstream maintains an image, etc.
I've done my best to represent each
REPO/maintainer.mdfile appropriately, but I might have missed some (or there might be something else a maintainer prefers be listed there, either more or less descriptive, for example), which would be welcome contributions following this change. ❤️ 👍Here's an example of what this looks like via GitHub, followed by a screenshot of the Hub's rendering of the same block (for simple comparison):
Quick reference
Where to get help:
the Docker Community Forums, the Docker Community Slack, or Stack Overflow
Where to file issues:
https://github.com/docker-library/golang/issues
Maintained by:
the Docker Community
Published image artifact details:
repo-info repo's
repos/golang/directory (history)(image metadata, transfer size, etc)
Image updates:
official-images PRs with label
library/golangofficial-images repo's
library/golangfile (history)Source of this description:
docs repo's
golang/directory (history)Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)