A bunch of new TODO items, based on skimming the first 100 of the 900

messages in my backlog. :(

1 files changed, 41 insertions, 7 deletions

diff --git a/TODO b/TODO
index d44f5d395..362f64ee3 100644
--- a/TODO
+++ b/TODO
@@ -6,7 +6,6 @@ The Mailman TODO List
     the 2.x series.
 
 Email Handling
-
     - Use VERP or DSN for address tracing, perhaps tied to the monthly
       password reminders, or VERPing the occasional regular message.
     - Use multiple subprocesses for MTA handoff, or divorce it
@@ -25,7 +24,6 @@ Documentation
     - manpages for the scripts in bin and cron
 
 General Web UI
-
     - NO DEAD ENDS
     - All web UI must be configurable so that it more easily
       integrates into an existing site's design.  Probably means using
@@ -34,6 +32,7 @@ General Web UI
     - A heirarchy of page designs and information: e.g. the most
       specialized of the following wins: site, virtual host, list,
       language, user.
+    - Web pages should never mention turned-off features.
 
 List Admin UI
     - Separate list admin role from list moderator role
@@ -43,7 +42,6 @@ List Admin UI
     - Allow "urgent" postings to all members by the list admin which
       bypasses normal digest delivery.
     - A button that will bundled and deliver a digest Right Now.
-    - Ability to set the next digest volume and issue number from the web
     - Allow the list-admin to require approvals for unsubs
     - Allow the admin to disable option settings by users
     - Ability to set defaults for the various user settings from the
@@ -55,6 +53,14 @@ List Admin UI
       addresses (but still sort case-insensitively).
     - Member management page should work better for humongous lists,
       both in terms of performance, and in usability
+    - Searching for members/addresses with regular expressions from
+      both the command line and web interface.
+    - New moderation choice: archive but don't send to list.
+    - New moderation choice: annotate and send to author for resubmittal.
+    - Make it easier for an admin who manages multiple lists to
+      handling pending requests sitting on all those lists.
+    - Ability to ban specific troublesome users (from posting,
+      subscribing, etc).  Posts from banned users would be discarded.
 
 List Member UI
     - Editing your user options should put you back to the edit-options page
@@ -67,10 +73,17 @@ List Member UI
       subscription.
     - Allow the user to get BOTH normal and digested delivery (but I
       still don't understand why someone would want this)
+    - More flexible digests: index digests (subject and authors only,
+      with URLs to retrieve the article)
+    - Allow users to subscribe without selecting a password and have
+      Mailman create a password for them.
+    - Timed vacations, allowing a user to postpone or discard email
+      for a certain number of days or weeks.
 
 Site Administrator's UI
-    - Allow the site admin to define list "styles", and list admins to
-      choose one of the canned styles to apply to their list.
+    - Allow the site admin to define list styles or themes, and list
+      admins to choose one of the canned styles to apply to their
+      list.
     - Full creation, deletion, renaming, etc. of lists through the web
       (and email?), including fixing aliases file updates.
 
@@ -81,9 +94,12 @@ Other Usability Improvments
       list admin).
     - A better strategy is needed for sub-lists and super-lists,
       including dealing with the resulting password reminders and
-      authorization to modify the sub & superlists.
+      authorization to modify the sub & superlists.  Majordomo2 is
+      reported to have some good features in this regard.
     - Add a limit on the number of posts from any one individual
       within a period of time (1 post per day, 10 per week, etc).
+    - Don't use the first public mailing list as the `originator' of
+      password reminders.
 
 Mailcmd interface
     - Provide an email interface to all administrative commands
@@ -93,16 +109,32 @@ Mailcmd interface
       resubscribe
     - Add -join and -remove addresses for easy subscription,
       unsubscription
+    - For email subscribes, keep an audit of where requests are coming
+      from, and send the original request headers in the confirmation
+      message.  Helps track down subscribe bombs.
+    - Investigate Majordomo2's email admin capabilities.
+    - Support the `which' command.
 
 Portability & architecture
     - Replace cron stuff with our own scheduling mechanism.
     - Get rid of the one-shot process model altogether in favor of a
       multithreaded monolithic architecture.
     - Better support for distributed processing
-    - Use a real transactional database for all information
+    - Use a real transactional database for all information, and allow
+      various bits of information to come from different sources (a
+      relational database, ZODB, LDAP, etc)
+    - Keep a members Real Name with their email address
     - Member profiles
     - Do a serious and thorough security audit
     - Allow lists of the same name in two different virtual domains
+    - More sophisticated attachment handling: strip and discard
+      attachments, post attachments (e.g. via WebDAV) and rewrite to
+      include URLs, etc.  Should be admin configurable based on MIME
+      type.  Check out Bill Bumgarner's work on this.
+    - Should include a --with-username=NAME option to configure (and
+      not require it be literally "mailman").
+    - Should be able to gather statistics, such as deliveries/day,
+      performance, number of subscribers over time, etc.
 
 Bounce handling
     - Make a distinction between disabled addresses due to bouncing
@@ -130,6 +162,7 @@ Pipermail + Archiving mechanism
       the Date: field is unreasonable (far in the future or far in the
       past).
     - In general the whole Pipermail subsystem needs a good rewrite.
+    - Ability to set the next digest volume and issue number from the web
 
 Code cleanup
     - Use all the new wizzy Python 2.0 features
@@ -138,6 +171,7 @@ Code cleanup
       target exceptions, when appropriate.
     - Turn all remaining string exceptions into class exceptions
     - Remove dead code.
+    - Unit and system test suite!