adds installation info to the readme
Adds the resource-ful route for feeds

The `resources :feeds` route will create mappings for the basic HTTP CRUD operations for the "feeds" resource, as can be seen in
this (partial) output of `rake routes`

    NAME  ACTION  PATH                     CONTROLLER#ACTION
    feeds GET    /feeds(.:format)          feeds#index
          POST   /feeds(.:format)          feeds#create
 new_feed GET    /feeds/new(.:format)      feeds#new
edit_feed GET    /feeds/:id/edit(.:format) feeds#edit
     feed GET    /feeds/:id(.:format)      feeds#show
          PUT    /feeds/:id(.:format)      feeds#update
          DELETE /feeds/:id(.:format)      feeds#destroy

The first name, "feeds", will generate the "feeds_path" helper, which is
exactly the method cucumber was complaining about before this commit.

At this point, now that the method exists, the cucumber spec looks like
this:

Feature: Feeds

  Background:                        # features/feeds.feature:2
    Given the following feeds exist: # features/step_definitions/steps.rb:1
      | name      | description                    |
      | homicides | zomg killing is pretty bad man |
      | fires     | really dude, arson?            |

  Scenario: View the list of feeds                         # features/feeds.feature:9
    When I visit the feeds list                            # features/step_definitions/steps.rb:9
      uninitialized constant FeedsController (ActionController::RoutingError)
      ./features/step_definitions/steps.rb:10:in `/^I visit the feeds list$/'
      features/feeds.feature:10:in `When I visit the feeds list'
    Then I should see the names for all the existing feeds # features/step_definitions/steps.rb:13

Failing Scenarios:
cucumber features/feeds.feature:9 # Scenario: View the list of feeds

1 scenario (1 failed)
3 steps (1 failed, 1 skipped, 1 passed)
0m1.010s

Which points to the absence of the controller these new routes map to.

More info can be found at: http://guides.rubyonrails.org/routing.html
Generates the feeds controller

Uses the controller generator:
 rails g controller feeds index

To create the controller "feeds" with a first action, "index"

The output is:

      create  app/controllers/feeds_controller.rb
       route  get "feeds/index"
      invoke  erb
      create    app/views/feeds
      create    app/views/feeds/index.html.erb
      invoke  rspec
      create    spec/controllers/feeds_controller_spec.rb
      create    spec/views/feeds
      create    spec/views/feeds/index.html.erb_spec.rb
      invoke  helper
      create    app/helpers/feeds_helper.rb
      invoke    rspec
      create      spec/helpers/feeds_helper_spec.rb
      invoke  assets
      invoke    coffee
      create      app/assets/javascripts/feeds.js.coffee
      invoke    scss
      create      app/assets/stylesheets/feeds.css.scss

So not only does it create the controller with the "index" method, it
also creates templates for rendering it.

At this point, the output of `rake cucumber` is: 

Feature: Feeds

  Background:                        # features/feeds.feature:2
    Given the following feeds exist: #
features/step_definitions/steps.rb:1
      | name      | description                    |
      | homicides | zomg killing is pretty bad man |
      | fires     | really dude, arson?            |

  Scenario: View the list of feeds                         #
features/feeds.feature:9
    When I visit the feeds list                            #
features/step_definitions/steps.rb:9
  1 OpenData::Application.routes.draw do
    Then I should see the names for all the existing feeds #
features/step_definitions/steps.rb:13
      expected to find text "homicides" in "Feeds#index Find me in
app/views/feeds/index.html.erb"
(RSpec::Expectations::ExpectationNotMetError)
      ./features/step_definitions/steps.rb:18:in `block (2 levels) in
<top (required)>'
      ./features/step_definitions/steps.rb:14:in `each'
      ./features/step_definitions/steps.rb:14:in `/^I should see the
names for all the existing feeds$/'
      features/feeds.feature:11:in `Then I should see the names for all
the existing feeds'

Failing Scenarios:
cucumber features/feeds.feature:9 # Scenario: View the list of feeds

1 scenario (1 failed)
3 steps (1 failed, 2 passed)
0m1.305s

Which means that the default behavior for an empty action in a rails
controller is to delegate control directly to the view rendering, which
explains why it's expecting to find text in the template already.

More info at
http://guides.rubyonrails.org/action_controller_overview.html
convention is to have _spec, not _specs :)
Adds failing spec for the feeds controller

In this step, instead of driving with cucumber, we go down one level and
test with a spec for the controller: we expect it to "assign" (set for
the view) an instance variable that contains the existing feeds.
makes the feed spec pass
makes the step expect titleized feed names just for kicks
Makes the feeds feature pass

But something is wrong! We skipped testing how the view is generated:
how, for example, is the name getting titleized?

We could test the views
(https://www.relishapp.com/rspec/rspec-rails/v/2-1/docs/view-specs/view-spec),
but, really, having templates with logic makes content negotiation hard:

* What if _every_ format (json, html, xml, hal) should have the feed name titleized?
* What if we change some css classes and the view spec has to be
  maintained to meet them, despite there not being a significant change
  in the data itself?

The solution is to have really dumb templates. But that means having
some object that applies the logic. It could be the model, but, no,
let's not make it the model! (moar fear-mongering links:
http://blog.codeclimate.com/blog/2012/10/17/7-ways-to-decompose-fat-activerecord-models/
)
Installs the draper gem to implement view-models (decorators)

https://github.com/drapergem/draper
Generates a decorator

using this command:

  rails g decorator feed
makes the feed decorator spec fail
makes the feed decorator spec pass by defining name method in the decorator
Makes the feeds controller expect using decorated feeds

The draper gem adds the assertions for checking that an object is
decorated
Decorates the feeds in the controller

We could use feeds.decorate instead of
FeedsDecorator.decorate_collection(feeds) but rails 3 breaks it:

https://github.com/drapergem/draper#collections
refactors the view to be more demeterish; scenario still passes