First step in two-part process to rename directories to kallithea.
This first step is to change all references in the files where they refer
to the old directory name.

Imported some of the GPLv3'd changes from RhodeCode v2.2.5.

This imports changes between changesets 21af6c4eab3d and 6177597791c2 in
RhodeCode's original repository, including only changes to Python files and HTML.

RhodeCode clearly licensed its changes to these files under GPLv3
in their /LICENSE file, which states the following:
The Python code and integrated HTML are licensed under the GPLv3 license.

(See:
https://code.rhodecode.com/rhodecode/files/v2.2.5/LICENSE
or
http://web.archive.org/web/20140512193334/https://code.rhodecode.com/rhodecode/files/f3b123159901f15426d18e3dc395e8369f70ebe0/LICENSE
for an online copy of that LICENSE file)

Conservancy reviewed these changes and confirmed that they can be licensed as
a whole to the Kallithea project under GPLv3-only.

While some of the contents committed herein are clearly licensed
GPLv3-or-later, on the whole we must assume the are GPLv3-only, since the
statement above from RhodeCode indicates that they intend GPLv3-only as their
license, per GPLv3§14 and other relevant sections of GPLv3.

Added --no-public-access / --public-access flags into setup-rhodecode
command to enable setup without public access

accept that repos are read-only - very convenient for testing.

Users are prompt to confirm they want to use read only paths.
org author: Mads Kiilerich

Implements #842 RhodeCode version disclosure.

- it's now implemented as visual option in settings

Add default for dashbord items and create default
settings in a sane way.

Changed default behaviour of dbmanage to fix issues with continues
migrations from multiple versions

Implemented simple gist functionality ref #530.

- creation of public/private gists with given lifetime
- rhodecode-gist CLI for quick gist creation

fixed default permissions population during upgrades
- it often happen that introducing new permission
caused default permission to reset it's state to installation
default.
new version makes sure that only missing permissions are
created while leaving old defaults

- Manage User’s Groups: create, delete, rename, add/remove users inside.
by user group admin.
In this case, a user's group can be owned by several people thru an owner user's group.

Some refactoring of naming, permission handling logic.
- remove some code duplicity as well as inconsistent naming

setup_rhodecode: fix --force-no - force_ask is tri-state

Missed in 260a7a01b.

follow Python conventions for boolean values

True and False might be singletons and the "default" values for "boolean"
expressions, but "all" values in Python has a boolean value and should be
evaluated as such. Checking with 'is True' and 'is False' is thus confusing,
error prone and unnessarily complex.

If we anywhere rely and nullable boolean fields from the database layer and
don't want the null value to be treated as False then we should check
explicitly for null with 'is None'.

Added missing migrations, and move update_repoinfo to RepoModel
migrations now update repo cache

Migration upgrades cache for lightweight dashboard
Fixed some migration issues

Added UserIpMap interface for allowed IP addresses and IP restriction access
ref #264 IP restriction for users and user groups

Implemented #379 defaults settings page for creation of repositories
- locking
- statistics, downloads
- repository type

implemented #663 Admin/permission: specify default repogroup perms
- added migration that adds new default permission for groups
- merged with patch from Vincent Caron

Remove null from revision column as for comments inside pull requests to work properly
new migration adds column for future simpler main page

migrations: fix old hook values
- nicer notifications

More fixes to upgrade procedure,
- fix missing section on hook
- fixed missing inherit_default_permission column

Step6a for migrations from 1.3.6
to 1.4.0

Implemented basic locking functionality.

- Reimplemented how githooks behave
- emaulate pre-receive hook
- install missing git hooks if they aren't already in repo

RhodeCode now has a option to explicitly set forking permissions. ref #508
- changed the way permissons on users groups behave. Now explicit set on user
is more important than permission set on users group

Added form for controlling mercurial extensions
added hggit also for future

sqlalchemy sessions cleanup in admin
Cleanup settings options

#227 Initial version of repository groups permissions system
- implemented none/read/write/admin permissions for groups
- wrote more tests for permissions, and new permissions groups
- a lot of code garden, splitted logic into proper models
- permissions on groups doesn't propagate yet to repositories
- deprecated some methods on api for managing permissions on
repositories for users, and users groups

garden
- unified logging formatting to use only %

fixed BCC problem in mailing library
- backported from my fixes in pyramid_mailer

added warning on sqlite when using migration.
Sqlite prior to 3.7 series are known to not support some
migration changes like table renames. Thus are failing.

fixed repo_create permission by adding missing commit statements
- added few tests for checking permission in UserModel
- added __json__() into get_dict() to fetch from it hybrid_properties and any additional custom properties
- code garden

commit less models
- models don't do any commits(with few exceptions)
- all db transactions should be handled by higher level modules like controllers, celery tasks

User usermodel instead of db model to manage accounts
- initial refactoring of models to handle rhodecode+api

Fixed #161 form saves the create repository permission.
routing update for users to support second form posting.
models updates