[tools] Started using ruby 2.1.0 for dev
[doc] Moved badges back to README
[doc] Outlined plans for upcoming release
[tools] Removed cane
[tools] Started using rubocop

The current plan of action is to generally accept all defaults and see
what new stuff I learn about ruby.

At present, the two current variations from the default are:

* The default cyclomatic complexity is too high, so go lower.
* Don't want to document my specs. I often create modules just for
  namespacing a describe.

There are hundreds of problems as it stands. Next couple commits should
bring that down and/or introduce new variations.
[tools, rubocop] Cleaned up most problems in spec/
[tools, rubocop] Cleaned up most problems in features/
[tools, cucumber] Eliminate 99% of env.rb?

I don't recall why I added this.. but things appear to run ok when I
remove it.. so..
[tools, travis] Started using 2.1.0
[tools, rubocop] Cleaned up all problems in examples/
[tools, rubocop] bin/ is now clear
[tools, rubocop] lib/reveal-ck/changers is now clear
[tools, rubocop] lib/reveal-ck/templates/ is now clear
[tools, rubocop] lib/reveal-ck/markdown/ is now clear
[tools, rubocop] Cleaned up all whitespace and switched to fail

I didn't know that some people preferred fail to raise in some
situations:

> Signal exceptions using the fail method. Use raise only when catching
> an exception and re-raising it (because here you're not failing, but
> explicitly and purposefully raising an exception).

From:

  https://github.com/bbatsov/ruby-style-guide
[tools, rubocop] lib/reveal-ck/config.rb is now clean..

Tests are passing.. but I swear a similar change to this caused failures
one time.
[tools, rubocop] Created exception for lib/reveal-ck.rb

So that people can 'require reveal-ck'
[doc] Documented RevealCK::VERSION
[rubocop] Increased allow complexity: 4 -> 5.

I'm going to re-write a bunch. Let's do the re-write and see how things
fall out.
[tools, rubocop] features/ is now clear