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

VersionEye Badges #35

Closed
reiz opened this issue Jul 3, 2013 · 8 comments
Closed

VersionEye Badges #35

reiz opened this issue Jul 3, 2013 · 8 comments
Labels
service-badge Accepted and actionable changes, features, and bugs

Comments

@reiz
Copy link

reiz commented Jul 3, 2013

Hey. Would be great if we would have VersionEye dependency badges who are conform with the other ones. Our current badges are self made and dancing out of the row. They are little bit to big. We tried to produce conform badges, but they are a little bit unsharp if we size them down to 18px high.
I appreciate every kind of support / input.

button-up-to-date copy
button-up-to-date

@reiz
Copy link
Author

reiz commented Jul 4, 2013

@olivierlacan we got them now sharp and online. But I guess there is still room for improvements :-)
Your feedback is highly appreciated.

dep_out-of-date
dep_unknown
dep_up-to-date
dep_update

@reiz
Copy link
Author

reiz commented Jul 5, 2013

The next step would be to make the yellow more dark. White on yellow is not optimal. And the green up-to-date badge needs to be aligned.

@reiz
Copy link
Author

reiz commented Jul 9, 2013

Just aligned the "up-to-date" badge with the other badges

dep_up-to-date

@reiz
Copy link
Author

reiz commented Jul 10, 2013

Allright! We have now another badge for out-of-date. A little more dark and readable :-)

dep_out-of-date

@olivierlacan
Copy link
Member

@reiz Thanks a lot for reaching out. We're working on providing Shields as a service fairly soon, which will solve the problem of actually generating badge PNGs.

As I've explained to other vendors, we like to stay away from promoting their brand through obvious branding and instead focus on the added value their service provides. While it's true that it refrains you from differentiating yourself from a service like Gemnasium for instance, it's a user-centered concern of providing a single coherent interface to open source repository meta-data.

Let me know if that makes sense, and my sincere apologies for taking centuries to get back to you. :-)

@reiz
Copy link
Author

reiz commented Aug 11, 2013

@olivierlacan Thanks for your response. I will check out the service. Actually the small eye in the badge is user driven. Some of our users complained about the first version because it looked to similar to Gemnasium ones. Would be cool if the service would support a small icon on the left or right site ;-)

@reiz
Copy link
Author

reiz commented May 14, 2014

@olivierlacan We are using currently the http://shields.io for our dependency badges. I consider this ticket as solved.

@reiz reiz closed this as completed May 14, 2014
@espadrine
Copy link
Member

That's great news!

espadrine added a commit that referenced this issue May 14, 2014
segiddins pushed a commit to segiddins/shields that referenced this issue May 21, 2014
@paulmelnikow paulmelnikow added service-badge Accepted and actionable changes, features, and bugs and removed needs-upstream-help Not actionable without help from a service provider labels Oct 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service-badge Accepted and actionable changes, features, and bugs
Projects
None yet
Development

No branches or pull requests

4 participants