aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorhttp://www.cse.unsw.edu.au/~willu/ <http://www.cse.unsw.edu.au/~willu/@web>2008-09-25 21:44:46 -0400
committerJoey Hess <joey@kitenet.net>2008-09-25 21:44:46 -0400
commita0b53cf26b3d72d06cfa6b20de764ad2d0ae7f06 (patch)
tree46bc27e92e873763dbed26563032213b7ead001e
parentfa763214e3efc826183f519c264089c4a976c431 (diff)
downloadikiwiki-a0b53cf26b3d72d06cfa6b20de764ad2d0ae7f06.tar
ikiwiki-a0b53cf26b3d72d06cfa6b20de764ad2d0ae7f06.tar.gz
Comments and links
-rw-r--r--doc/todo/Better_bug_tracking_support.mdwn13
1 files changed, 12 insertions, 1 deletions
diff --git a/doc/todo/Better_bug_tracking_support.mdwn b/doc/todo/Better_bug_tracking_support.mdwn
index 628a67fc8..1a810ad55 100644
--- a/doc/todo/Better_bug_tracking_support.mdwn
+++ b/doc/todo/Better_bug_tracking_support.mdwn
@@ -44,7 +44,18 @@ be embedded to the source code repository commit messages.
>> look like a wikipage anymore, but rather something like the Debian
>> BTS web-interface, but it would still benefit from wikilinks to the
>> documentation in the wiki etc.
->>
+
+>>> I think it is useful to look at these things separately:
+>>>
+>>> * Bug numbers: See above.
+>>> * Automatic timestamps on comments: this already exists with the inline directive.
+>>> * Email interface: You can certainly get an rss feed of what changes in the wiki.
+>>> * You didn't mention [[todo/structured_page_data]] but that is, I think, part
+>>> of what you seem to be saying.
+>>> * [[todo/tracking_bugs_with_dependencies]] is also important.
+>>>
+>>> -- [[Will]]
+
>> About the commit message interface: I was thinking about a project
>> architecture where the code is kept in a separate revision control
>> system branch than the metadata (blog, wiki, BTS). This would IMHO