Describe the scope of Quaidan.

Users of Quaidan can easily discover what Quaidan does. The settled
scope helps me to recognize the time for the pulic release.
Choose the MIT license.

I don't want to restrict the applicability of Quaidan. The MIT license
allows the most and restricts the least.
Untrack files that are generated by build tools.

I use the template provided by GitHub. It is available from
https://github.com/github/gitignore/blob/master/Python.gitignore
Add configuration for Vagrant.

The virtual machine starts an Apache server with a running balancer
manager that can be used to test Quaidan.
Create the setup script.

This script allows for building, distributing, installing and testing
Quaidan by Python's distutils.
Create parser for the balancer manager page.
Use Travis CI for continuous integration.

The CI server is available at https://travis-ci.org/stefanbirkner/quaidan

I use Travis because it provides some features that make
working with an open-source project easier.
* It [builds pull requests.](http://docs.travis-ci.com/user/pull-requests/)
* The CI server configuration is part of the project. Hence Travis CI can be used by every developer who forks this repository. She just has to activate Travis CI for her clone.
* It builds and tests Quaidan with different versions of Python (2.6, 2.7, 3.2, 3.3 and 3.4).
* I can install an Apache HTTP Server with mod_proxy_balancer as endpoint for the tests.