Fix browser test failures under ruby 2.0

Make sure that the regex (or matcher) is always the first argument in
calls to `assert_match` and `assert_not_match`.
Make travis notifications quieter

Fixes the .travis.yml syntax so the `use_notice` and `skip_join` options
are respected.
Fix running firefox browser tests

In firefox it seems that the hover then click combo only works for
elements that are visible in the viewport. When an element is outside
the viewport these tests fail with a
`Selenium::WebDriver::Error::ElementNotVisibleError` when run with the
firefox driver.

This patch uses javascript to scroll the required element into view
before interacting with it, which fixes these failures when I run
against firefox locally. Hopefully it will also fix the travis build.
Try running popit tests against 0.10 on travis

They pass fine for me locally, and since this is the current node
version, and has been for some time, we should be testing against it for
any obvious bugs.
Only show the master branch build status in README

Failing pull requests and feature branches are to be expected.
Change .travis.yml to allow IRC notifications

I *think* because the channel mode is +n the travis bot needs to join to
be able to post notices.
Add a test demonstrating data loss bug

This is a failing test to demonstrate the bug reported in
https://github.com/mysociety/popit/issues/261.
Fix browser editing bug

*sigh* This ended up being a *much* simpler fix than I started with.
Because we're overriding the `set` method for person and organisation
models, we can't expect backbone to always call it with all the fields,
this was causing some of the data to be lost when saving under certain
circumstances.

This fix simply returns early from `nest` if the attributes don't include
the nested model.
Merge pull request #262 from mysociety/browser-editing-bug

Browser editing bug
Update npm-shrinkwrap.json

Includes the dependencies for the latest version of popit-api.

Updated using latest npm, so this should work correctly with newer
versions of npm, older version will simply ignore fields that they don't
understand.
Fix broken documentation links

Use absolute links rather than relative ones to prevent 404s
Upgrade production node version to v0.10.24

If the installed node version doesn't match the configured version, it
will be upgraded.

This also switches to using the pre-built binaries from nodejs.org,
which significantly reduces the install time for a new version of node.
Add process.versions output to dev helpers

This makes it easier to see which version of node you're currently
running, along with other useful information about which software node
was compiled with.
Build all branches except production on travis
Rebuild npm-shrinkwrap.json using latest node

After clearing out my npm cache (`npm cache clear`) and removing my
local node_modules directory I did a fresh install using the shrinkwrap
file from master, then re-ran `npm shrinkwrap` and it gave this output.

It seems to install correctly under the latest 0.8.x with npm 1.2.30, as
well as under 0.10, so I can't see any problems with it.
deploy to production - version bump to 0.0.17
Merge branch 'master' into production
Update static assets