From c8b26c51aa67fc9345b624e36aab6f819e7eed74 Mon Sep 17 00:00:00 2001
From: James Moger <james.moger@gitblit.com>
Date: Sun, 25 Nov 2012 11:35:31 -0500
Subject: [PATCH] Gitblit Certificate Authority revisions. Eliminate certificate scripts.
---
docs/05_roadmap.mkd | 27 ++++++---------------------
1 files changed, 6 insertions(+), 21 deletions(-)
diff --git a/docs/05_roadmap.mkd b/docs/05_roadmap.mkd
index b29f622..14ad8c1 100644
--- a/docs/05_roadmap.mkd
+++ b/docs/05_roadmap.mkd
@@ -8,37 +8,22 @@
* Eclipse: create plugin to enumerate repositories and delegate cloning to EGit
* Manager: support federation RPCs
* Manager: redesign ref indicators in log, search, and activity views to support multiple local branches, remote branches, and tags
+* Gitblit: Serve repositories on root URL rather than /git (investigate JGit 1.2 GitFilter)
### TODO (medium priority)
* Gitblit: editable settings page in GO/WAR
-* Gitblit: tag repositories and offer views of repositories by tag (issue 27)
-* 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
-* Gitblit: Consider using Git-style config file instead of Java properties file for user storage (users.config vs. users.properties)
- * this would allow for additional fields per user without bringing in a database
-
-### TODO (low priority)
-
-* Gitblit: Blame coloring by author (issue 2)
-* Gitblit: View binary files in blob page (issue 6)
### IDEAS
-* Gitblit: aggregate RSS feeds by tag or subfolder
+* Gitblit: Re-use the EGit branch visualization table cell renderer as some sort of servlet
+* Gitblit: diff should highlight inserted/removed fragment compared to original line
+* 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 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: Blame coloring by author (issue 2)
--
Gitblit v1.9.1