diff: show whitespace

It could be considered to use the VisibleWhitespaceFilter instead ...

remove: when removing a repo don't rename its .hg/.git folder

There is no need to do that ... and doing it will just make analysis and
recovery harder and confuse other tools recursing the repos, such as hgweb.

urlify: use look behind and ahead in hash regexp

This makes it match hashes only separated by a single whitespace - such as
space or newline.

pull requests: don't make reviewers mandatory

It will be hard to get a review approved without reviewers, but they can be
added (or removed) later and there is no reason to fail because they are
missing in the initial version.

status: don't calculate status of whole repo when given empty list

SQLAlchemy would warn that it was a bad idea.

setup.cfg: remove http://www.pylonshq.com - it is nolonger available

https://groups.google.com/d/msg/pylons-discuss/cypPARmbh_0/lGA6nsE40fIJ
recommends removing it.

user edit: always define c.EXTERN_TYPE_INTERNAL (issue 3)

It is needed by user_edit_profile.html when user_edit.html includes it because
.active='profile'. Some non-obvious code paths could lead to that - such as
editing other user's password.

Instead, set the value it in the controller initialization.

Use Conservancy's Kallithea Committee address as author_email.

the setup.py needs an author_email setting. Since this is a fork, the
author_email should be the individuals responsible for the fork. This
address reaches the Kallithea Committee at Conservancy.

Align and update the outdated ini files and templates

Change default database for development.ini to sqlite

db: tweak configuration of branding self references

For RhodeCode compatibility:
echo "BRAND='rhodecode'" > kallithea/brand.py

SETTINGS_PREFIX for identifiers (e.g., db table names) incl. project's name.

kallithea.SETTINGS_PREFIX is a variable string used as a prefix for specific
external identifiers, such as database table names (and likely later form
fields), so that the name of the project need not necessarily be encoded into
data.

This setting is configurable so that compatibility with old, similar
databases can be maintained at the users' request.