TODO list gardening

diff --git a/TODO b/TODO
index e522e93c011324034c753885e8bebdbb857e7712..c90558df3332090c5753700ef85ce0d182e47a55 100644 (file)
--- a/TODO
+++ b/TODO
@@ -2,26 +2,10 @@ control.pl:
  - followup <BUGID> (shortcut for "graft <BUGID> !")
  - <BUGID> == "it" (most recently mentioned bug in this message)
  - way to reference the root of the thread. (From iwj)
- - add message-id of control (and reply) mails to refs for bugs?
-   - i.e. as a graft.
-   - How to handle control message which touches more than one bug?
-     - adding them all -- replies to the control reply cause bug
-       threads to converge.
-     - ignoring threads for replies to control replies means those
-       threads aren't tracked.
-     - control reply for each bug touched?
- - need to consider control messages which aren't a reply as well as
-   those which are.
- - how to handle control messages which don't go to the list.
-    - insert control messages into DB too? Dedup with copy from the
-      list?
-    - reject with reply only to sender?
  - nicks for owners? (e.g. ijc => ian.campbell@citrix.com) (From gwd)
  - quiet control messages (From tjd)
     - how and where to record their actions.
     - bug-dist list is sufficient perhaps?
- - SEO
-    - make sure there is an index page of all bugs for them to start from
  - Enable Perl taint mode?
 
 bugs:
@@ -36,19 +20,21 @@ bug.pl:
 bugs.pl:
  - summary of the status of the bugs
  - search -- double check for XSS
- - header to describe how to file a bug
+ - search by:
+    - owner
+    - title
+    - tags
+    - full text search handled by search engines.
+ - SEO
+    - make sure there is an index page of all bugs for them to start from
 
 message.pl:
  - Write it
    - return entire raw message
    - return individual parts
 
-meta:
- - page on how to use, command reference etc, installed by makefile
-
-database:
- - proper DB not sqlite.
+documentation:
+ - have some
 
 other:
- - configure ML address and use
  - navigation between bug.pl and bugs.pl etc