From 6f46fa34d3078399acaa962a89900ac5db3a6116 Mon Sep 17 00:00:00 2001
From: James Moger <james.moger@gitblit.com>
Date: Tue, 27 Dec 2011 17:31:50 -0500
Subject: [PATCH] Documentation.

---
 docs/05_roadmap.mkd |   22 ++++++++++++++++++----
 1 files changed, 18 insertions(+), 4 deletions(-)

diff --git a/docs/05_roadmap.mkd b/docs/05_roadmap.mkd
index 511e9bb..bb7aaad 100644
--- a/docs/05_roadmap.mkd
+++ b/docs/05_roadmap.mkd
@@ -7,19 +7,27 @@
 
 * Eclipse: create plugin to enumerate repositories and delegate cloning to EGit
 * Manager: support federation RPCs
-* Manager: RSS feed reader tab  
+* Manager: redesign ref indicators in log, search, and activity views to support multiple local branches, remote branches, and tags
 
 ### TODO (medium priority)
 
 * Gitblit: editable settings page in GO/WAR
-* Gitblit: tag repositories and offer views of repositories by tag (issue 27)
-* Gitblit: aggregate RSS feeds by tag or subfolder
-* Gitblit: investigate create-on-push possibility
+* Gitblit: investigate create-repository-on-push.
+    * Maybe a new user role to allow this?
+    * Maybe a server setting to disable this completely?
+    * Pusher/Creator becomes repository owner and can then manipulate access lists, etc?
 * Gitblit: Clone Repository feature (issue 5)
     * optional scheduled pulls
     * optional automatic push to origin/remotes?
     * optional manual push to origin/remotes?
 * Gitblit: Lucene integration with multi-repository search (issue 16)
+* Gitblit: Repository regex substitutions should be stored in .git/.config, not gitblit.properties
+* Gitblit: Consider allowing git:// protocol using JGit
+    * new setting *git.allowGitProtocol* to enable/disable git:// protocol
+    * unrestricted repositories would have anonymous RW git:// access
+    * push-restricted repositories would have anonymous R git:// access
+    * clone-restricted repositories would prohibit git:// access
+    * view-restricted repositories would prohibit git:// access
 
 ### TODO (low priority)
 
@@ -28,4 +36,10 @@
 
 ### IDEAS
 
+* Gitblit: implement branch permission controls as Groovy pre-receive script.  
+*Maintain permissions text file similar to a gitolite configuration file or svn authz file.*
+* Gitblit: consider user-subscribed email notifications for a repository branch as a built-in feature.  
+*There is a sample Groovy post-receive hook script which can send emails.*
+* Gitblit: aggregate RSS feeds by tag or subfolder
+* Gitblit: Consider creating more Git model objects and exposing them via the JSON RPC interface to allow inspection/retrieval of Git commits, Git trees, etc from Gitblit.
 * Gitblit: Stronger ticgit integration (issue 8)

--
Gitblit v1.9.1