Group project-related stats into a class.

Reduce number of instance variables available to the views.
Replace raw SQL with AR-type query.
Group context-related pieces in a class
Encapsulate counts and totals into a class.

Move queries out of the view and into the model layer.
Inline helper method
Inline last pieces into StatsController#index

We can now skip the before filter that sets instance variables.
Encapsulate dependencies of stats index page

This may be a bit extreme.

It's modeled after the ideal "rails way".

In the controller, we now know the name of a single resource. It
doesn't happen to be backed by a database table, but it does know all
about the task of collecting stats, leaving the controller concerned
with just munging params and rendering stuff.

I called the resource `IndexPage`, to avoid the temptation of trying to
reuse it, which can get pretty messy.

Later, if a better abstraction appears, it should be fairly painless to
alter.
restore the french locale file
Merge pull request #169 from kytrinyx/index-page

Encapsulate dependencies of stats index page
add the mocha stubbing and mocking library
add test coverage for when we don't have any users

It wasn't being covered in the functional test for this controller.
Check schema.rb into source control

This practice is "strongly recommended."
http://guides.rubyonrails.org/migrations.html#schema-dumps-and-source-control
Use db:schema:load instead of db:migrate
Revert "Use db:schema:load instead of db:migrate"

This reverts commit 3c5f28869bb5901b8001c2402154809261b1355b,
which did not function properly on the continuous integration server.