allauth: Enable OpenID and Persona login support by default
allauth: Redesign the social account registration page
allauth: Document new features in the release notes

Also move it up in the roadmap.
allauth: docs: Document allauth/social auth support
allauth: Drop a redundant dir attribute
allauth: Disable third party authentication support by default

Support will be enabled and ready if users uncomment the apps in
INSTALLED_APPS.
Also document the allauth settings accordingly.
Fix bug introduced in c209b1ee
docs: build with warnings as errors
docs: fix broken hyperlink
docs: ignore specs/ directory when building
docs: fix location of pootle_logo.png
cleanup: no need for special Pootle db setup script

Well documented elsewhere and better scripted now.
Tests: added basic requirements file
Tests: integrated py.test with setuptools test command

Allows to run tests by executing `python setup.py tests`. This will still
do nothing because the existing tests haven't been adapted yet.

The code has been brought from the py.test good practices documentation
available at http://pytest.org/latest/goodpractises.html
Tests: removed obsolete tests

Conflicts:
	pootle/apps/pootle_store/tests.py
Tests: moved existing tests to the high-level tests directory

These have been copied and slightly adapted. Running the tests will still
fail.

Conflicts:
	tests/models/unit.py
Tests: allow running tests using `make test`

Sets up a virtual environment for testing, installs the dependencies and
executes the test runner. This is just a starting point and will need to
be adapted if there's a will to integrate with CI tools.

Conflicts:
	Makefile
Tests: allow setting test-specific settings

Basically test environments will ignore the usual settings/90-*.conf
files, whereas settings/90-tests(-local).conf will be read.

The provided test settings file is just a starting point for now.

Conflicts:
	pootle/settings.py
Tests: added pytest fixtures

These pytest-style fixtures replicate the initial dataset that the
`initdb` command creates. Ideally we should find a way not to repeat code
in both ends.

Any fixtures defined in modules under the `tests/fixtures/` umbrella will
be automatically loaded when running the tests.
Tests: no need for a `nonpriv` user

We already have some predefined users (nobody, default, admin) that can be
reused as fixtures.