------------------------------------------------------------
revno: 129
committer: Benoît PIERRE <benoit.pierre@gmail.com>
branch nick: sloecode
timestamp: Wed 2011-09-21 19:18:13 +0200
message:
  Allow _-. in person identifiers.
------------------------------------------------------------
revno: 130
committer: Benoît PIERRE <benoit.pierre@gmail.com>
branch nick: sloecode
timestamp: Wed 2011-09-21 19:18:23 +0200
message:
  Allow _-. in project identifiers.
------------------------------------------------------------
revno: 131
committer: Benoît PIERRE <benoit.pierre@gmail.com>
branch nick: sloecode
timestamp: Thu 2011-09-22 11:33:09 +0200
message:
  Add support for using PAM for authentication.
------------------------------------------------------------
revno: 132
committer: Benoît PIERRE <benoit.pierre@gmail.com>
branch nick: sloecode
timestamp: Thu 2011-09-22 11:41:33 +0200
message:
  Add on-the-fly user creation when a new user logs in.

  Useful when using an external authentication system (like PAM).
------------------------------------------------------------
revno: 133
committer: Benoît PIERRE <benoit.pierre@gmail.com>
branch nick: sloecode
timestamp: Thu 2011-09-22 11:48:48 +0200
message:
  Do not allow user creation and password changes when using PAM.

  Add allow_password_modification and allow_user_creation helpers:

  * allow_password_modification: return True if changing password is allowed

  * allow_user_creation: return True if user creation is allowed

  Both are not allowed when using PAM.

  Update person-create and person-update page: do not show password changes are
  not allowed.

  Do not show 'Admin/Person/Create New' entry in navigation bar when user
  creation is not allowed.
------------------------------------------------------------
  Fix user creation to work when password modification is not allowed.

  Even when using PAM for authentication, it can still be useful to create users:
  - an administrator can manage the details of user creation.
  - even if the user don't exist on the PAM side, and won't be allowed to connect
    to the web interface, he may still interact with the code hosting server.
------------------------------------------------------------
revno: 135
committer: Benoît PIERRE <benoit.pierre@gmail.com>
branch nick: sloecode
timestamp: Thu 2011-09-22 20:24:58 +0200
message:
  Remove left-over debug trace in helpers.
------------------------------------------------------------
revno: 136
committer: Benoît PIERRE <benoit.pierre@gmail.com>
branch nick: sloecode
timestamp: Thu 2011-09-22 20:30:08 +0200
message:
  Add support for public projects.

  A public project will automatically be read-only accessible by all users,
  without the need to manually add them as observers.
------------------------------------------------------------
revno: 137
committer: Benoît PIERRE <benoit.pierre@gmail.com>
branch nick: sloecode
timestamp: Thu 2011-09-22 20:33:33 +0200
message:
  Fix "permission denied" trace when accessing another user repository.
------------------------------------------------------------
revno: 138
committer: Benoît PIERRE <benoit.pierre@gmail.com>
branch nick: sloecode
timestamp: Fri 2011-09-23 18:29:05 +0200
message:
  Quick hack to allow read-only access to all user repositories.
------------------------------------------------------------
revno: 139
committer: Benoît PIERRE <benoit.pierre@gmail.com>
branch nick: sloecode
timestamp: Fri 2011-09-23 21:33:20 +0200
message:
  Change logfile name to include username when launching 'bzr sc-serve'.
------------------------------------------------------------
revno: 140
committer: Benoît PIERRE <benoit.pierre@gmail.com>
branch nick: sloecode
timestamp: Mon 2011-09-26 15:21:04 +0200
message:
  Quick hack: change branches display name.

  Use path relative to containing repository, instead of nickname.
------------------------------------------------------------
revno: 141
committer: Benoît PIERRE <benoit.pierre@gmail.com>
branch nick: sloecode
timestamp: Mon 2011-09-26 15:23:06 +0200
message:
  More fine-grained control for projects.

  Read-only access for:
  * everybody when project is public
  * all project members if project is private

  Read/write access for:
  * managers and developers of the project
------------------------------------------------------------
revno: 142
committer: Benoît PIERRE <benoit.pierre@gmail.com>
branch nick: sloecode
timestamp: Mon 2011-09-26 19:09:43 +0200
message:
  Quick hack: change branches display name.
------------------------------------------------------------
revno: 143
committer: Benoît PIERRE <benoit.pierre@gmail.com>
branch nick: sloecode
timestamp: Mon 2011-09-26 19:09:55 +0200
message:
  More fine-grained control for projects.