Add `twitter-bootstrap-rails` gem.

Also, use release versions of `seed-fu` and `cucumber-rails`.
Install bootstrap assets and scaffold events.

For now, it just Bootstrap-ifies the CRUD interface.
Create "_round" partial to render a round table

For some reason, it doesn't load couples which did not receive any marks
for the round. This has something to do with the `Round.includes` call.
I could try replacing it with a whole bunch small queries. Worry about
scaling later...
Add `quiet_assets` gem.

It removes log messages about static assets, making the log much nicer
to read.
Undo some eager association load in round display

For some reason I can't understand (probably related to the way `LEFT
OUTER JOIN` works), using the eager-loading associations caused couples
which did not receive any marks in a round to be omitted entirely.
Undoing this, and performing a separate query for each cell of the
table, resolves that problem. With enough caching, the performance
should be good enough that the extra queries don't completely kill
things.
Cache the round fragment.

In production mode, this vastly speeds up rendering. Since the round
will not change after it has been built, this is a big win, as the cache
will remain valid forever.
Use `Round` partial to render `Event` results

Now renders the complete event result page!
Remove SASS (using Less instead)

I don't know either well enough to have any preference, but Bootstrap
uses Less, so just go with that.
Add basic borders and zebra stripes for rounds

Makes it much easier to read.
Add some more informative classes to elements
Cache event results pages on event objects.

This way, the page does not need to be rebuilt after the first time.
Render the event body in a partial.

Just splits up things a bit more.
Make width of the results table cells uniform.
`_couple`  partial now takes a `round` parameter

Rather than passing the `sub_rounds` and `adjudicators` as separate
arguments, just pull them from the `round`.
Couple method `recalled_from?(round)`
Helper for couple
Modify database.yml and add ".travis.yml"

Hopefully, this is all that is needed to get Travis up and running.
Add explicit dependency on 'yard' gem.

This seems to solve the "uninitialized constant YARD" error. Will have
to see whether it is the case on Travis as well.
Disable email notifications for build status.
Cache gem bundle to speed up Travis testing.