Talking with @sferik it seems like as more badge versions are contributed to this project, either by being added or being modified it might become tedious to clean up the SVG source files from artifacts dumped by Adobe whenever Illustrator touches the files.

To prevent having to do cleanup manually it would be nice to use a simple Rake task to fetch all the required dependencies. We also want to be able to clean stuff up before someone contributes back to the project. And finally, eventually we'll want to be able to export everything properly to PNG whenever needed. That last one is still being talked about in #23 since we haven't come up with a satisfying solution, but let's be hopeful. 😸

Prerequisites

• Homebrew

Features

• install all necessary fonts & dependencies (svg libraries, etc)
• clean up the AdobeCrap™ comments and weird inconsistent tabs & spaces
• hopefully export everything to PNG in a consistent matter so we don't need Illustrator, ever. Ever. Additionally it would make it easier to output @2x badges down the line.

/cc @ackerdev

Noticed that Crate.io is using a slightly wonky Shield-like badge. https://crate.io/packages/requests/

Alright, let's make a list of the services that currently use discrepant badges so we can get in touch with them, involve them in this initiative and get them shielded in due form.

Services

• Travis is live!
• Code Climate is live!
• Gemnasium is live!
• Gemfury is coming soon!
• Coveralls is live!

These look great and we'd like to use them. To do so, we need a few tweaks:

• Change "GPA" text to "code climate" so it's a bit more descriptive. As pointed out, GPAs are a US-centric concept and even when GPA is understood it's not clear how that relates to the project (specifically, it's the code). So "code climate" is also a descriptor of the number included (in addition to the brand, of course).
• We're going to round to one decimal place, so we need images from 0.0 - 4.0.
• We also need a state for "unknown" (would be very very rare, but possible). Probably just a "?" instead of a number is fine, in grey.
• The numbers should map to colors as follows:
  • 3.6 - 4.0 dark green
  • 2.6 - 3.5 light green
  • 1.6 - 2.5 yellow
  • 0.6 - 1.5 orange
  • 0.0 - 0.5 red

If you could help me out with those things, I'd really appreciate it, and can get started on rolling these out. We'd need PNGs as the final product (41, I think, for 0.0-4.0 + unknown state).

Awesome work on this!

-Bryan

Bintray as a new player could have the same badges as PyPI and other repos (# of downloads, latest version, etc).

The [REST API](https://bintray.com/docs/api/ makes this quite easy; the only special thing to take care of is keeping an eye on the rate limits, and cache data so that not every shield request leads to an API request.

Over on #15 you'll see that Gittip has acquired Shields, as far as @olivierlacan and I are concerned. However, in the spirit of openness and transparency, I'm opening this ticket to give anyone a chance to raise objections to this deal. Sorry we rushed ahead without consulting the community properly. :-(

There's a parallel ticket at gratipay/gratipay.com#1307, and I've recorded my own reasoning behind Gittip's interest over there.

The plan is to proceed with the deal but leave this and gratipay/gratipay.com#1307 open for a few days to surface any objections.

Suggested by @pjz in IRC. Waddya think, @olivierlacan @ackerdev?

shields or #shields.io?

Let's log to http://botbot.me/, as with #gittip and #aspen.

We should serve 500s as a PNG.

Traceback (most recent call last):

  File "aspen/website.py", line 76, in handle_safely
    response = self.handle(request)
  File "aspen/website.py", line 109, in handle
    response = request.resource.respond(request)
  File "aspen/resources/dynamic_resource.py", line 47, in respond
    exec self.pages[1] in context
  File "/app/www/%first/%second.png.spt", line 76, in <module>
    transformed = transform_and_cache(transform_key, first, second, color)
  File "/app/www/%first/%second.png.spt", line 28, in transform_and_cache
    first, second, color = transform(first, second, color)  # expensive HTTP
  File "shields_io/services.py", line 60, in gittip
    receiving = float(json.loads(fp.read())['receiving'])
  File "aspen/json_.py", line 95, in loads
    return _json.loads(*a, **kw)
  File "json/__init__.py", line 338, in loads
    return _default_decoder.decode(s)
  File "json/decoder.py", line 365, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "json/decoder.py", line 383, in raw_decode
    raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded

https://app.getsentry.com/shields/shields/group/7771652/

BuildHive is a CI service.
Example of their badge here...
It would be great if they could be involved in this project.

Some ideas for general purpose badges:

• sandbox
• early development
• in development
• production
• unstable
• released
• stable
• abandoned (see stillmaintained ?)
• looking for contributors
• ...

• Revert d41b039
• Reprocess shields with appropriate colors for code climate

3.6 - 4.0 dark green
2.6 - 3.5 light green
1.6 - 2.5 yellow
0.6 - 1.5 orange
0.0 - 0.5 red

There can't be that many people using Badgr.co yet but I know there's a few. I'm going to start tweeting and linking here to hopefully let people know that Badgr.co is going away. I suppose we could leave some overlap with Shields.io once that's launched. Probably for how much traffic Badgr.co is getting a month of overlap would be fine (it's double the SSL cost $20/mo).

Following #15, @olivierlacan is going to hold onto shields.io for the immediate future. At some point before registration is up (2014-02-18) we should transfer this to Gittip, LLC.

https://github.com/gittip/badgr.co/issues?state=open

I'm thinking it would be neat to start using our own badges now that we have a real codebase. 😄

AKA "Free as in Freedom" the shit out of the shield creation process.

To both remove the need for proprietary tools like Photoshop and Illustrator, and to automate the creation of new badges, we should do the following:

• Create new, clean template SVG
  Remove illustrator noise, use semantic class names for easy node manipulation. Make note of gradients for automation in the generator script.
• Create a generator script to parse and edit the SVGs, and spit them out as PNGs
  Nokogiri to parse SVG XML. Make it easy to define the required badges that will be generated. See https://github.com/olivierlacan/shields/issues/15#issuecomment-13878052 for a guide to convert the SVGs to PNGs using imagemagick
• Create a rake script to install font & deps via homebrew

Hi guys,

it seems that Travis CI's green badge has been updated to use a flasher green version:

https://github.com/olivierlacan/shields/blob/master/travis/travis_passing.png

Could we get same green for Gemnasium to stay consistent?

Sorry to ask this but I'm really not familiar with that svg and png's generation stuff.

Thanks

@jbowes has a cli that should be much faster than the one we're using.

badges/buckler#6

http://pugx.github.io/
Similar to PyPI, uses shields but has very broken rendering right now. Reach out to PUGX when service gets rolling.

Per http://www.youtube.com/watch?v=CZ0lgVWGSEs. Details forthcoming on #15 ...

Old badgr.co repo: https://github.com/gittip/badgr.co/

Investigate options for embedding the font into the SVG so as to allow the SVG to be easily portable.
Possibilities include:

Convert OpenSans to an SVG font* and embed it into the SVG
Remove unnecessary characters; should only need unaccented alphanumerics, dash, and period. For static badges, would be possible to remove all glyphs that the badge does not use. Be wary of excessive filesize.

Convert OpenSans to an SVG font* and link externally
Best option, but may be a concern as Firefox restricts cross-domain font linking.

Convert to Outlines
If all else fails, static badges can be converted to outlines and it will work just fine. Leaves us with no solution for dynamic badges ala gemfury's gem version badge.

*Licensing should not be an issue, but double check to be safe that it does not conflict.
References:
http://nimbupani.com/about-fonts-in-svg.html
http://frabru.de/c.php/article/SVGFonts-usage

We have few languishing issues from vendors that either reached out, or that we discovered were trying to using the style we set forth but didn't quite succeed in doing so.

As soon as shields.io is live and kicking we should reach out to all these folks and urge them to update their shield implementations. 😃

Reticketed from #15.

Hello,

I'm working on Semaphore and would like to get it "shielded".

We uses badges for the following build statuses:

• passing
• pending
• failing
• unknown

Build badges from here:

suite our color taste but we need a badge for the "unknown" status instead of the "error" status.

Could you create those badges for us or what is the standard workflow?

We've got a placeholder at http://shields.io/.

We should recruit a talented designer to do up some branding (logo, favicon), and a homepage.

It would be nice to have a shield for Semver that could represent version numbers in a project.

As opposed to, say, doing this:

Just noticed this earlier.

Whereas the other ones do:

Here's a draft blog post announcing the acquisition of Shields by Gittip (#43):

http://blog.gittip.com/private/59222865731/tumblr_ms1wozSypi1ryzw25

@olivierlacan When I get the go-ahead from you I will publish that. Let me know what we should change there. I've also sent you an email with login info for the Shields_io Twitter account (which also gets you access to manage the Shields.io Gittip account).

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.

If the width is consistent, badges embedded in text will not change the flow depending on status

• First it's a Microsoft font, which makes it a no-no.
• Second it behaves poorly with all-caps and numbers as you can see below:

CNAME to origin-shields-io.herokuapp.com (link).

How about it, @olivierlacan? :-)

My thinking is that shields.io itself will be on a CDN, and origin.shields.io will be the origin server behind it.

I have an account at MaxCDN that I'm planning to use for this, if there are no objections.

How bad do the existing badges look on High-DPI/Retina machines?

Is it possible versions that are dense enough to look good everywhere?

Hello,

First of all, thank you for this project! It's amazing, simple and beautiful. I think you did a great job.

Based on it, I started a project for badges for Cocoapods (Objective-C package manager) and I've created badges for a pod (package) version and another for the platforms it supports (iOS, OSX). Don't worry, I gave you credits for the SVG used: http://fjcaetano.github.io/cocoapod-badges/

The guys from Cocoapods got super excited, and even created an API for me (since the first version was a little hack on their site :P) and they tweeted it to spread it to other developers. https://twitter.com/CocoaPods/status/342238471865372674

Now, if it's not asking much, I'd also like your help sharing it. Simply adding a link to my repo on your services list would be a great help!

Btw, I'm serving my badges dynamically, even though I'm serving them as svg and not png. I saw there's an issue on that matter, so why don't you take a look at my project?

Let's discuss what we will need for the possibility of offering Shields as a Service. What considerations do we need to make to ensure that it is feasible and robust?

Originally posted by @jhermann on the old badgr.co issue tracker.

This would create a badge from a link like

• http://badgr.co/jenkins-ci/«scheme»/«host»/«path_parts...»/job/«jobname»/todo.png
• Example: http://badgr.co/jenkins-ci/http/huschteguzzel.de/hudson/view/jhermann/job/dput-webdav/todo.png

Note that this introduces an URL schema to support "many of the same" type of services (e.g. "Any Jenkins hosted somewhere on the web").

Badge would look like “[TODO][hi# / norm# / lo#]” (2nd field color green/yellow/red, depending on the TODO counter classes being >0), from these API calls:

• first, call «joburl»/tasks example
• tack on api/json to the redirect Location you get (urljoin) example
• decode JSON, render counters into image

If that works, things could be extended with …/build.png (build status), …/build_no.png (build #), and so on (there's a lot of data in the API).

I noticed while working on #20 that the PSD could use some improvements that might make it easier going forward to transition Shields into a service (which I'm interested in helping with, by the way).

It might be helpful to convert shadows, gradients and color overlays to all use "Normal" blending. This makes it easier for something like ImageMagick or even CSS to build badges from composite layers. And these badges are sufficiently simple where that's entirely possible.

Also, the gradient in the PSD extends well outside of the bounds of the badge mask. That's fine for exporting badges but it would be nice to have the point-to-point gradient more strictly defined, again for ease in composition with ImageMagick and/or CSS.

It would be nice to have a shield that indicates 100% test coverage.

I realize that a lot of discussion about Gittip badges as been included in #15. Really should be its own thing.

Here are the main messages relevant to this topic:

• https://github.com/olivierlacan/shields/issues/15#issuecomment-19158912
• https://github.com/olivierlacan/shields/issues/15#issuecomment-19159252
• https://github.com/olivierlacan/shields/issues/15#issuecomment-19205554
• https://github.com/olivierlacan/shields/issues/15#issuecomment-19280778
• https://github.com/olivierlacan/shields/issues/15#issuecomment-19326305
• https://github.com/olivierlacan/shields/issues/15#issuecomment-19338709

As a quick sidenote, I didn't catch it during the conversation but if you display $46/wk on the donations badge you risk people thinking it costs $46/wk to donate to this project. That's the first thing that jumped to my mind.

It is more informational the route of [donations | $46/wk ] but it's ambiguous.

I don't think it's inappropriate to use the Gittip badge as a piece of information regarding the fact that *the maintainers of this project would like you to contribute $1/wk to support it`.

Hence why ultimately, [ donate | $1/wk ] ends up making a lot more sense to me. For the unambiguity and the intention-revealing factor. Yes, it's a call to action. I can live with that.

/cc @whit537

Hi. I am working on http://www.versioneye.com and we offer dependency badges for Java, PHP, Ruby and Node.JS Libraries. Specially the PHP & Java community asked for this feature. Currently we are using the Gemnasium Shields from this project. Here is a short blog post about the VersionEye badges:
http://versioneye.wordpress.com/2013/05/08/versioneye-dependency-badges/

Would be cool to have some unique shields to avoid confusion with the Gemnasium community.

was: Push GitHub to support image width & height in Markdown

Just reading up on Multimarkdown I found this: https://github.com/fletcher/MultiMarkdown/wiki/MultiMarkdown-Syntax-Guide#anchor-and-image-attributes

Real bummer that there's nothing similar in either standard markdown or GFM. Could we push GitHub to support it so that people don't necessarily have to use HTML (in some places it's not possible, I'm sure) when they eventually want to use Retina badges? Maybe by making GFM support it ourselves?

@olivierlacan I think we lost collaborators when we transferred the repo. Can you re-add them?

https://github.com/gittip/shields.io/settings/collaboration

[Reticketed from #15.]

The folks at https://david-dm.org/ are using Shields-like badge that are just different enough to stand out (see dredd).

Would be nice to reach out to them when Shields.io is live.

Either an AI or SVG version would be convenient to find coordinates for dynamic badge composition.

@joshk has requested a 5th shield for the travis-ci set.

Create an 'unknown' variant of the travis ci shield (grey).

(Also draft a set of shields labeled 'travis ci' instead of 'build').