aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-02-10 21:49:56 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-02-10 21:49:56 +0000
commit4f8aff02ed3fdbbf57b72fbc6ca8b586dcd51a96 (patch)
treee84853bd2bd6c0823abbd518104777a6f318cda0
parent879e5e17c7cb64fcff336d800ee77e9ae5e907ba (diff)
downloadikiwiki-4f8aff02ed3fdbbf57b72fbc6ca8b586dcd51a96.tar
ikiwiki-4f8aff02ed3fdbbf57b72fbc6ca8b586dcd51a96.tar.gz
web commit by JoshTriplett
-rw-r--r--doc/todo/BTS_integration.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/todo/BTS_integration.mdwn b/doc/todo/BTS_integration.mdwn
new file mode 100644
index 000000000..a22f4bdaa
--- /dev/null
+++ b/doc/todo/BTS_integration.mdwn
@@ -0,0 +1,5 @@
+Given network access when building the wiki, ikiwiki could retrieve information from bug-tracking systems and apply that information to BTS links. For instance, consider how links from one bugzilla bug to another use strikeout formatting for links to fixed bugs, and use the status and summary of the bug to the link as a title.
+
+This seems somewhat difficult, as ikiwiki would need to maintain a cache of the remote BTS information, and know how to talk to various types of BTS. CPAN modules exist to solve this problem for some types of BTS.
+
+--[[JoshTriplett]]