summaryrefslogtreecommitdiffstats
path: root/docs/05_roadmap.mkd
Commit message (Collapse)AuthorAgeFilesLines
* Final documentation of 1.2.0 releasev1.2.0James Moger2012-12-311-2/+4
|
* Implemented optional create-on-pushJames Moger2012-10-211-4/+0
| | | | | | | | | | | | | | | | If this feature is enabled then permitted users can automatically create a repository when pushing to one that does not yet exist. Permitted users are administrators and any user with the CREATE role. If the pushing account is an administrator, the created repository may be located in any folder/project space. This reposiory will inherit the server's default access restriction and authorization control. The repository owner will be the pushing account. If the pushing account is a regular user with the CREATE role, the repository can only be located in the account's personal folder (~username/myrepo.git). This repository will be VIEW restricted and accessible by NAMED users. The repository owner will be the pushing account.
* Preliminary implementation of server-side forking (issue 137)James Moger2012-09-291-1/+0
| | | | | | | | | | | | | | | | | | 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.
* Draft project pages, project metadata, and RSS feedsJames Moger2012-09-071-2/+0
| | | | | | This is an in-progress feature to offer an interface for grouped repositories. This may help installations with large numbers of repositories stay organized. It also will be part of a future, more advanced security model.
* Final documentation of 1.1.0 releasev1.1.0James Moger2012-08-251-1/+0
|
* DocumentationJames Moger2012-07-111-6/+0
|
* DocumentationJames Moger2012-03-201-2/+0
|
* Documentation. Find bugs. Organized imports.James Moger2012-01-091-0/+3
|
* Unit testing. Documentation.James Moger2011-12-281-8/+5
|
* Documentation.James Moger2011-12-271-1/+0
|
* Groovy push hooksJames Moger2011-12-161-1/+4
|
* Implemented ConfigUserService. Fixed and deprecated FileUserService.James Moger2011-12-041-2/+1
|
* Documentation. Add javadoc and source jars to the gbapi download.James Moger2011-11-111-2/+14
|
* Display more refs (still not all) per rss entry. Misc ui tweaks.James Moger2011-11-101-0/+1
|
* Documentation.James Moger2011-11-091-0/+1
|
* Revised branch rendering. Added ref rendering to message column.James Moger2011-11-031-1/+0
|
* DocumentationJames Moger2011-10-281-11/+12
|
* Documentation.James Moger2011-10-261-0/+30