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

Add image/information to our dockerhub repo #1196

Open
sambhav opened this issue Jun 8, 2021 · 3 comments
Open

Add image/information to our dockerhub repo #1196

sambhav opened this issue Jun 8, 2021 · 3 comments
Labels
status/ready Issue ready to be worked on. type/chore Issue that requests non-user facing changes.

Comments

@sambhav
Copy link
Member

sambhav commented Jun 8, 2021

Description

The Cloud Native Buildpacks Docker Hub repos (buildpacksio and (cnbs)(https://hub.docker.com/u/cnbs)) look pretty sketchy. cnbs is understandable, given that it seems like we only host sample/internal images (though we do reference it in our docs), but given that buildpacksio is a bit more external (we will soon be referring to it in our tekton task (tektoncd/catalog#434), and it is our "official" lifecycle/pack image), we should probably spend some effort making it a bit more trustworthy.

Proposed solution

Add a description/logo to buildpacksio/pack

Additional context

buildpacks/community#27

@sambhav sambhav added status/triage Issue or PR that requires contributor attention. type/chore Issue that requests non-user facing changes. labels Jun 8, 2021
@importhuman
Copy link
Member

Is there a way I can work on this without having access, or is the issue for maintainers?

@sambhav
Copy link
Member Author

sambhav commented Oct 1, 2021

This issue can currently only be fixed by maintainers. @samj1912 to figure out a label to tag such issues in the future.

@natalieparellano
Copy link
Member

FWIW the information for the lifecycle is referenced here: https://github.com/buildpacks/lifecycle/blob/main/IMAGE.md (we wanted it to live in GitHub so that fixes/changes could be submitted by the community).

I could imagine that a contributor might be able to PR the text to a file in the pack repo and then a maintainer could copy it over.

With that said I'll mark this as ready, but @buildpacks/platform-maintainers please re-label if I'm wrong.

@natalieparellano natalieparellano added status/ready Issue ready to be worked on. and removed status/triage Issue or PR that requires contributor attention. labels Mar 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/ready Issue ready to be worked on. type/chore Issue that requests non-user facing changes.
Projects
None yet
Development

No branches or pull requests

3 participants