-Added help messages for all targets
-Added help target
-Divided targets into blocks for easy understanding
-Added new target install-js for npm install
-Used new target in install and css
-divided install target into 3 targets
    install-python
    install-test
    install-js
-Updated i18n traget names
-Added install-migrations-testing-requirements target
-Used install-migrations-testing-requirements in test_migrations
-Updated .PHONY

Since there is no demo or us site anymore we can simplify the structure
somewhat by moving the sandbox one directory up

The flake8 directive was specified in tox.ini and setup.cfg while only
one is used. Also remove the lint.sh script and move the code to the
Makefile.

travis: Run py.test --cov=oscar instead of coverage run

The container only runs an uwsgi process and uses the
default sandbox settings for now.

The demo site was not kept up to date with the recent changes in Oscar
due to time contraints. It should be moved to a separate demo repository
in the future.

This might be resurrected in a separate repository in the future.

Usage:
  npm install
  npm run build
  npm run start

This also removes the --process-dependency-links argument to pip install
since this was only required for the unreleased version of the
django-tables package.

To support Django 1.8, we are needing a fix in tables2. It is pending a
merge in https://github.com/bradleyayers/django-tables2/pull/245

Let's hope that we'll get a release soon.

Unfortunately, this change requires that we re-enable the deprecated
--process-dependency-links to pip install. I welcome any ideas for a
better approach.

This removes all the bits and bobs where we referenced South, or added
some code supporting it. Documentation will be updated in a later
commit, together with other Django changes.

It's useful to fail on too many lint errors, but right now I have a
scenario where I'm happy to ignore lint errors, but Travis doesn't
report whether the tests passed because it stopped at the linting phase.

By first running the test suite, this behaviour is remedied.

We moved the Oscar code into src/, so those commands need updating.

This should have multiple advantages:
- We're not mixing eggs with the flat installs from pip
- Given a reasonably current pip, we can take advantage of wheels
- Using pip for both allows for easier reasoning about dependencies

This is to avoid an issue on Travis where Django 1.7 is installed when
it shouldn't be.

The file was removed in af3c381d to remove Vagrant, but it served a
dual purpose as requirements to test our suite of migrations. It's
resurrection will hopefully let Travis pass again.

Taking lead from 22041aab99

The puppet provisioning of the Vagrant box has been broken for ages due
to floating dependencies. I don't want to support it anymore since
Docker images are almost ready - hence why it goes.

We also drop the "allow_failures" section for Pythons 3.x on Travis.
They should pass consistently now.

I've also adjusted the 'travis' make target to not install Oscar so this
can be called separately as part of the Travis build. Hence, build
errors are reported differently from tests failing.

Motivated by 51bf7280, this change adds a new make target to find parts
of the codebase that need changing after some event has happened. It
also adds an example TODO.

This crude and destructive script helps create migrations for both South
and Django's native migrations framework. I'm happy to leave plenty of
room for improvement so that the King of Bash (aka @codeinthehole) can
do his thing.

This commit also enforces South 1.0. It's a backwards compatible release
which explicitly is meant to help the migration; it makes both our and
our users life's easier. Notably, it first looks for a south_migrations
directory before falling back to the migrations directory in an app.
That nicely avoids any conflicts between migration files between the two
migration frameworks.

Where I previously thought that renaming HTML/CSS is more hassle than
it's worth, @mbertheau convinced me that to update a codebase, a general
search-and-replace is the best approach already and will catch any
HTML/CSS changes.

I also missed to deprecate the min_variant_price properties.

I started looking at this because on the mailing list, having the UK as
only shipping country led to confusion. This is mostly due to the
shipping address form hiding the country field if there's only one
country enabled, but all the validation then requiring UK postcodes and
phone numbers.

It's bothered me for a while that we're using a fixture to populate the
countries, which is at risk of becoming stale.
pycountry offers an excellent data source for a list of countries, so I
polished an existing management command to use it to populate the
country database.

This commit has two immediate effects:
* New setups will use a more current country database
* By default, all countries will be marked as shipping countries

pycountry also ships with localised names of the countries, which should
allow us to populate the database with localised country names.