summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
Diffstat (limited to 'TODO')
-rw-r--r--TODO28
1 files changed, 17 insertions, 11 deletions
diff --git a/TODO b/TODO
index f0c914f..af23e34 100644
--- a/TODO
+++ b/TODO
@@ -2,16 +2,10 @@ welcome to the TODO file.
== short-range TODO ==
-fix the patch display/markup
+remove hardcoded url parsing
- given the disk space requirements, the patches are not automatically
- generated any longer. an as-of-yet unwritten cgi script will handle
- such requests.
-
-don't nuke/reinit the whole patch tracking tree
-
- this also implies that some kind of garbage collection takes place
- to remove versions that are no longer being tracked
+ pagehandler currently assumes installation under a certain subdir,
+ which isn't at all necessary.
better handling of more exotic patch systems
@@ -22,8 +16,19 @@ better handling of more exotic patch systems
code cleanup from really ugly stuff (look for XXX)
+dead code removal/cleanup
+
+ after switching a few design decisions, there's some code that's no longer
+ used or should be renamed/moved (i.e. writers/templates)
+
== medium-range TODO ==
+review db design
+
+ the db schema design is most likely less than optimal, the use of triggers
+ to emulate foreign keys is novel but likely we can remove a few columns and
+ use rowids instead, and possibly lower/optimise the remaining queries.
+
remove all the os.system calls
lots of temporary ducttape via os.system that should go away
@@ -35,8 +40,9 @@ make prettier pages
decide how much should be cgi-based and how much should be written
- there's no reason why the other pages couldn't also be generated from
- a cgi, if we desired.
+ there's no reason why the entire system can't be generated via cgi-based
+ accessing, but the question is whether it should be, or whether certain
+ componenets should remain static.
== long-range TODO ==