summaryrefslogtreecommitdiffstats
path: root/docs/04_releases.mkd
diff options
context:
space:
mode:
authorJames Moger <james.moger@gitblit.com>2012-09-29 23:40:46 -0400
committerJames Moger <james.moger@gitblit.com>2012-09-29 23:40:46 -0400
commit1e1b85270f93b3bca624c99b478f3a9a23be2395 (patch)
tree8dfcbd8ca4813d2a42455c62cae3b433d8c0c28a /docs/04_releases.mkd
parent0d531b187e123dea5e83b5b7d4749478f26254c1 (diff)
downloadgitblit-1e1b85270f93b3bca624c99b478f3a9a23be2395.tar.gz
gitblit-1e1b85270f93b3bca624c99b478f3a9a23be2395.zip
Preliminary implementation of server-side forking (issue 137)
The fork mechanism clones the repository , access restrictions, and other config options. The app has been updated throughout to handle personal repositories and to properly display origin/fork links. In order to fork a repository the user account must have the #fork role, the origin repository must permit forking, and the user account must have standard clone permissions to the repository. Because forking introduces a new user role no existing user accounts can automatically begin forking a repository. This is both a pro and a con. Since the fork has the same access restrictions as the origin repository, those who can access the origin may also access the fork. This is intentional to facilitate integration-manager workflow. The fork owner does have the power to completely change the access restrictions of his/her fork.
Diffstat (limited to 'docs/04_releases.mkd')
-rw-r--r--docs/04_releases.mkd13
1 files changed, 9 insertions, 4 deletions
diff --git a/docs/04_releases.mkd b/docs/04_releases.mkd
index 454ce65c..30582d53 100644
--- a/docs/04_releases.mkd
+++ b/docs/04_releases.mkd
@@ -17,10 +17,15 @@ If you are updating from an earlier release AND you have indexed branches with t
#### additions
-- added support for X-Forwarded-Context for Apache subdomain proxy configurations (issue 135)
-- delete branch feature (issue 121, Github/ajermakovics)
-- added line links to blob view at the expense of zebra striping (issue 130)
-- added RedmineUserService (github/mallowlabs)
+- Added simple project pages. A project is a subfolder off the *git.repositoriesFolder*.
+- Added support for personal repositories. This builds on the simple project pages.
+Personal repositories are stored in *git.repositoriesFolder*/*~username*. Each user with personal repositories will have a user page, something like the GitHub profile page. Personal repositories have all the same features as common repositories.
+- Added support for server-side forking of a repository to a personal repository (issue 137)
+In order to fork a repository to a personal clone, the user account must have the *fork* permission **and** the repository must *allow forks*. The clone inherits the access restrictions of its origin. i.e. if Team A has access to the origin repository, then by default Team A also has access to the fork. This is to facilitate collaboration. However, the fork owner may change access to the fork and add/remove users/teams, etc as required.
+- Added support for X-Forwarded-Context for Apache subdomain proxy configurations (issue 135)
+- Delete branch feature (issue 121, Github/ajermakovics)
+- Added line links to blob view at the expense of zebra striping (issue 130)
+- Added RedmineUserService (github/mallowlabs)
#### changes