With this tests running on saucelabs should be less flaky, as they
recently have been, e.g.,
https://saucelabs.com/beta/tests/a17cda7d243b4343aad1c83d54979b76/logs

For now let the tests run on chrome-on-travis. This is becuase
sauce_connect addon is not available on forks:
https://docs.travis-ci.com/user/sauce-connect/

Tests on all browsers will work when you push changes to your local repo
fork, though.

Sample report from an integration test:
https://saucelabs.com/beta/tests/7e6958fd51d44abfbb7a5e7a1efe132a/commands
See, e.g., screencast that you can play or see history.

BREAKING CHANGE: Now node 4 is required to build the project. This is
because protractor 3 requires is. I decided to make the switch now,
because it would happen anyway at some point.

With this change I've gone through all ESLint rules at:
http://eslint.org/docs/rules/ and added all of them that I feel make
sense to the project.

This will allow us to focus on business logic of our code, rather than
on style discussions, which are now better guarded thanks to ESLint and
clang-format.

On the final note: it does not matter what concrete lint rules are
enforced (e.g., semicolons or nor). The important part is that they are
enforced by a tool and we do not spend time dicussing about them.

Addresses: #66

This change reformats all files according to clang-format rules (the
same that Angular JS has) and forces the files to comply with the
formatting.

This change makes it possible to run tests, integration tests and lint
on Travis CI. It also prepares a special Gulp task to perform the same
activities locally. This is handy when, e.g., sending a pull requrest.

Next change will actually implement some tests for the backend.

This is to have unified codebase from the beginning of the project.

Added a few simple rules to the linter and fixed all errors through the
codebase. This will allow to wire it up to some automatic checks.

This is a basic config that allows to run the tests. Subsequent pull
requests will use it in Gulp tasks to run protractor tests over
development and production code.

Next commits will use this configuration to lint the codebase.

This is a sample Angular application written in ES6 with modules. It has
sample unit and integration tests. It was generated with a help of
Yeoman.

Don't mind what the application does right now. I'll use it for a next
few days to verify that build system is working. Then it will be
revamped.