README.rst (shown on github and also at the start of the html docs) shall
be like an elevator speech - convince readers in a very short time.
this is most important, everything else can come after we got the reader's interest.
include README into docs to avoid duplication.
also include CHANGES into docs.
add developer docs, move examples from tox.ini there
add separate support docs
remove glossary, most of what was there can be understood by an admin from context
move attic and compatibility note to the end
the usage of some py.test features in the previous locking changesets somehow broke the test environment.
it seems to help to point py.test to some specific package or module (and not just invoke "py.test" without arguments).