Update to API v2 (#11)

Removes:
* accounts
* users

Adds:
* organizations
* collaborators
* event fields
* pivots
* trends

Updates:
* comments
* errors
* events
* projects

.travis.yml

@@ -1,13 +1,20 @@
 language: ruby
 rvm:
+- 2.4.1
+- 2.2.2
 - 2.1.0
 - 2.0.0
 - 1.9.3
-- jruby-18mode
 - jruby-19mode
-- 1.8.7
-- rbx-2
-notifications:
-  hipchat:
-    rooms:
-      secure: pxU3BZq7lQKFdbEzzysH9tFzHYPWh/AfqJ3yG1lois4D4UW+29ranTtOPR8qUChXSM6KhC4uOXwekTDOQTTALO95483gEYyGvXCTtomhSrZEBCv7Ngl9IHRtPU0nPuuQBo2v95S/KlInuEsL/gwaKQO8iXItevdJZnRChFaKDuA=
+
+before_install:
+- gem install bundler -v 1.12
+- gem update --system
+- bundle --version
+- gem --version
+
+install:
+- bundle _1.12.0_ install --with "$GEMSETS"
+
+script:
+- bundle _1.12.0_ exec rake

CONTRIBUTING.md

@@ -0,0 +1,40 @@
+# How to contribute
+
+1. [Fork](https://help.github.com/articles/fork-a-repo) the [library on GitHub](https://github.com/bugsnag/bugsnag-api-ruby)
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit and push until you are happy with your contribution
+4. Push to the branch (`git push origin my-new-feature`)
+5. Run the tests and make sure they all pass:
+
+    ```
+    rake spec
+    ```
+
+6. Create a [Pull Request](https://help.github.com/articles/using-pull-requests)
+
+Thank you!
+
+## How to release
+
+If you're a member of the core team, follow these instructions for releasing bugsnag-api-ruby.
+
+### First time setup
+
+* Create a Rubygems account
+* Get a member of the platforms team to add you as contributor on bugsnag-ruby in Rubygems
+
+### Every time
+
+* Update `CHANGELOG.md`
+* Update the version number in `bugsnag-api.gemspec`
+* Update `README.md` if necessary with changes to the interface or configuration
+* Commit/push your changes
+* Release to rubygems
+
+  ```
+  gem build bugsnag-api.gemspec
+  gem push bugsnag-api-[version].gem
+  ```
+* Create a new GitHub release, copying the changes from the change log
+
+