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

Badge icons and NuGet #6

Open
onovotny opened this issue Sep 24, 2019 · 7 comments

Comments

@onovotny
Copy link
Contributor

commented Sep 24, 2019

In addition to displaying the badges on a project's readme, I think it'd be useful to the ecosystem if the badges could be displayed in the NuGet UX (website, clients). I'd suspect that most developers aren't going to a GitHub site to determine quality. Having those badges visible where they look for packages could be a huge benefit and help users make a decision based on a project's maturity level.

@onovotny

This comment has been minimized.

Copy link
Contributor Author

commented Sep 24, 2019

/cc @rrelyea as NuGet PM

@richlander

This comment has been minimized.

Copy link
Collaborator

commented Sep 24, 2019

Indeed. The proposal touches on this, and I've had initial conversations with the NuGet team on this. Let's assume that this will happen.

@anangaur

This comment has been minimized.

Copy link

commented Sep 25, 2019

This should just get enabled as part of ReadMe integration. i.e. when we allow developers to put a the markdown file in the nupkg and is displayed as extended description. The badges come automatically.

@onovotny

This comment has been minimized.

Copy link
Contributor Author

commented Sep 25, 2019

@anangaur I would want to see this on the top-level search results, not buried in the readme.

@anangaur

This comment has been minimized.

Copy link

commented Sep 25, 2019

Got it. We are discussing about quality indicators and it does fit in that. Will keep you posted as we make progress.

@richlander

This comment has been minimized.

Copy link
Collaborator

commented Sep 25, 2019

Cool. I'll also setup some time with you @anangaur on what I see as the best next steps for NuGet to integrate into this.

@terrajobst

This comment has been minimized.

Copy link

commented Sep 27, 2019

Oren's ask obviously would mean integration work in the client UI as well. I could even see this going to be a step further and in conjunction with the trust features NuGet has built. For instance, a project might want to state "I'm a level X library, so please block me from accidentally depending on a library that isn't at least level X as well". Same goes for app authors in conservative environments that require the highest maturity level for dependencies. I suppose both will need a way to deal with exceptions tho.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.