Consider adding license badge from shields.io

[ssokolow]

There are three reasons why I think you should at least consider using a badge from shields.io to indicate the license in README.md:

1. It allows you to comfortably put the license at the top of the file so people dropping in don't have to scroll down past the examples. (I don't know about you but I always check a library's license before I consider the merits of its API.)
2. Depending on the user, it may be significantly more eye-catching than plain text.
3. Having a section (License) with just one word in it (MIT) looks unpolished.

Here's the badge and the markdown involved:

[![MIT licensed](https://img.shields.io/badge/license-MIT-blue.svg)](https://raw.githubusercontent.com/hyperium/hyper/master/LICENSE)

...or you could pull it dynamically from the GitHub or crates.io metadata APIs by using one of these image URLs:

https://img.shields.io/github/license/hyperium/hyper.svg
https://img.shields.io/crates/l/hyper.svg

[reem]

@ssokolow I agree this would be nice. If you're up to PR the changes to the README, I'd be happy to review/merge.

[ssokolow]

Sure. My main concern is that I'm not sure what ordering to use.

In my projects, I tend to block things out as "[CI] [Coverage] [Static Analysis] [Release Metadata] [License]"

...but, here, the colours make me want to organize it like this instead...

[reem]

I'd prefer build, crates, coverage, license. Since the colors might change, we shouldn't organize by color.

[ssokolow]

I normally wouldn't organize by colour either, but that crates.io badge really throws off my usual rules.

Normally, my rationale is:

1. The left 2/3rds change colour to indicate problems and should be a mass of green.
2. The right 1/3rd doesn't indicate status and should be a neutral blue.
3. Source badges to the left of release badges (coverage before crates)
4. License can be counted as either source or release

That way, I can use the row of badges as a simple status dashboard.

Sticking the crates badge so close to the status-indicating badges knocks my brain off the fast-path evaluation because I actually have to read to determine whether the orange indicates a problem rather than scanning my eyes over a row of colours.

Perhaps this so that it's clear that the "blue stuff" section has already started?

Ideally, there'd be an option to use a crates.io badge in a colour that either means "all good" (green) or lies outside the "green through red" spectrum that intuitively indicates status. (blue, black, white, grey, etc.)

(Just a suggestion. If it's not up for discussion, I'll make the PR now.)

[reem]

@ssokolow sorry for just dropping this, I just found it again and still want to do this. Feel free to PR build, coverage, license, crates.