diff options
| author | viega | 1998-06-02 03:24:59 +0000 |
|---|---|---|
| committer | viega | 1998-06-02 03:24:59 +0000 |
| commit | eb83e6271152f7cc8fb7a2b67a998716fc1b8ed1 (patch) | |
| tree | 02a54c4efb195c416488956515bb1969486887f7 | |
| parent | b298b38c55f9364a4b42571e55dfc8e9e8cfddf2 (diff) | |
| download | mailman-eb83e6271152f7cc8fb7a2b67a998716fc1b8ed1.tar.gz mailman-eb83e6271152f7cc8fb7a2b67a998716fc1b8ed1.tar.zst mailman-eb83e6271152f7cc8fb7a2b67a998716fc1b8ed1.zip | |
Removed todo.html. Instead, I'm going to check in the script which is
used to generate todo.html from the TODO file in the top of the CVS
tree, just in case someone feels like mirroring these pages off the
public CVS tree. Not having todo.html checked in will encourage us to
modify just one TODO list.
| -rw-r--r-- | admin/www/todo.html | 124 |
1 files changed, 0 insertions, 124 deletions
diff --git a/admin/www/todo.html b/admin/www/todo.html deleted file mode 100644 index 018fbb180..000000000 --- a/admin/www/todo.html +++ /dev/null @@ -1,124 +0,0 @@ -<HTML><HEAD><TITLE>The Mailman TODO list</TITLE></HEAD><BODY> -<H1> The Mailman TODO list </H1> -<H2>Categories:</H2> -<UL> -<LI><FONT SIZE=+1><A href=#c1>Bugs</A></FONT></LI> -<LI><FONT SIZE=+1><A href=#c2>Documentation</A></FONT></LI> -<LI><FONT SIZE=+1><A href=#c3>General Web UI</A></FONT></LI> -<LI><FONT SIZE=+1><A href=#c4>List Admin UI</A></FONT></LI> -<LI><FONT SIZE=+1><A href=#c5>List Member UI</A></FONT></LI> -<LI><FONT SIZE=+1><A href=#c6>Site Administrator's UI</A></FONT></LI> -<LI><FONT SIZE=+1><A href=#c7>Email Handling</A></FONT></LI> -<LI><FONT SIZE=+1><A href=#c8>Mailcmd interface</A></FONT></LI> -<LI><FONT SIZE=+1><A href=#c9>Portability concerns</A></FONT></LI> -<LI><FONT SIZE=+1><A href=#c10>Bounce handling</A></FONT></LI> -<LI><FONT SIZE=+1><A href=#c11>Pipermail + Archiving mechanism</A></FONT></LI> -<LI><FONT SIZE=+1><A href=#c12>Code cleanup</A></FONT></LI> -<LI><FONT SIZE=+1><A href=#c13>Misc</A></FONT></LI> -</UL> -<HR> -<A NAME=c1><H3>Bugs</H3> -<UL> -<LI> Turning off bounce processing doesn't seem to work.</LI> -<LI> Turning on non-member post exclusion doesn't seem to work.</LI> -<LI> "Stale" addresses don't update properly when new bounces come in (stale means we had some bounces, but delivery to that address started working again before we booted them from the list)</LI> -</UL> -<A NAME=c2><H3>Documentation</H3> -<UL> -<LI> A FAQ (esp. for the web page)</LI> -<LI> A detailed feature list</LI> -<LI> A high level feature list</LI> -<LI> A user's guide</LI> -<LI> A site-admin's guide</LI> -<LI> A list-admin's guide</LI> -<LI> More in-place documentation</LI> -<LI> A developer's guide w/ Architecture and API info, etc.</LI> -</UL> -<A NAME=c3><H3>General Web UI</H3> -<UL> -<LI> Add a navigation sidebar to all web pages - central links, and list-specific links for list-specific pages.</LI> -<LI> Implement cookies for edithtml and admindb</LI> -<LI> Make sure when settings are changed, there is always some sort of confirmation!</LI> -</UL> -<A NAME=c4><H3>List Admin UI</H3> -<UL> -<LI> The list admin should be able to turn off the security mechanisms such as confirmation and passwords if he deems it necessary.</LI> -<LI> Make it so mass-subscribe doesn't hang waiting for the mail transport to do all delivery.</LI> -<LI> Allow the admin to remove posts from the database w/o email notification.</LI> -<LI> Time out admin requests, and have them auto-fail after that period.</LI> -<LI> Allow the admin to edit posts in the database (put a header in the post noting that it was edited by a moderator, however!)</LI> -<LI> Have the option for moderator passwords, so that moderators don't have access to the general list options.</LI> -<LI> An -urgent address for each list that may only be posted to by the list admin. It will seem to be sent to the whole list, but will deliver to everyone ASAP, and not wait for digests.</LI> -<LI> Better options for the policy on bundling digests (periodic w/ arbitrary periods, size based, a combo of the two, etc).</LI> -<LI> A button that will bundle a digest right now (tm).</LI> -<LI> A generic error template page.</LI> -<LI> An option for setting the precedence header.</LI> -<LI> Make the MM-tags accept useful options where appropriate.</LI> -<LI> Revamp the admindb user interface, it's fairly clunky (include a decent cataloging mechanism based on the file system).</LI> -</UL> -<A NAME=c5><H3>List Member UI</H3> -<UL> -<LI> Editing your user options should put you back to the edit-options page. </LI> -<LI> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers.</LI> -<LI> An option to change your email address.</LI> -<LI> Allow users to specify a different address for password reminders (w/ confirmation), or come up w/ a better strategy for remailing lists (could be done as the default, given a generic filter mechanism).</LI> -</UL> -<A NAME=c6><H3>Site Administrator's UI</H3> -<UL> -<LI> Make a web based site admin UI for adding lists, deleting lists, etc.</LI> -<LI> Use a better storage mechanism for the site admin password</LI> -<LI> Improve list deletion by requiring a valid password (from the shell script)</LI> -</UL> -<A NAME=c7><H3>Email Handling</H3> -<UL> -<LI> Implement a reasonable administrivia filter (but less likely to misfire than majordomo's).</LI> -<LI> Implement a more general (form-based, like the netscape email filter) filtering/bouncing/etc. mechanism.</LI> -<LI> Allow for programs to run that perform filtering / reformatting.</LI> -<LI> Improve confirmation code so that the user only need respond to a message.</LI> -<LI> Make confirmation messages NOT process the message body as commands.</LI> -<LI> Set asside messages IMMEDIATELY as a rescue mechanism... make sure no mails are ever lost, even if there turned out to be a bad Mailman bug.</LI> -</UL> -<A NAME=c8><H3>Mailcmd interface</H3> -<UL> -<LI> Provide an email interface to administrative commands.</LI> -</UL> -<A NAME=c9><H3>Portability concerns</H3> -<UL> -<LI> Use portable file locking</LI> -<LI> Replace cron stuff with our own scheduling mechanism</LI> -</UL> -<A NAME=c10><H3>Bounce handling</H3> -<UL> -<LI> Add more patterns for bounce handling</LI> -<LI> Occasionally remove stale bounce entries</LI> -<LI> Send mail to people that are being removed w/o their knowlege (even though they're likely not to get it).</LI> -<LI> Clean the code up, make it more robust and efficent (see also bugs)</LI> -</UL> -<A NAME=c11><H3>Pipermail + Archiving mechanism</H3> -<UL> -<LI> Hook it back up in the default distribution</LI> -<LI> Search engine for archives</LI> -<LI> Format the list of archives nicely by default, perhaps in a table: <table border=3> <tr><td>Archive</td> <td>Date</td><td>View by:</td></tr> <tr><td>Vol. 1</td> <td>Q4, 1998</td><td>DATE THREAD AUTHOR </td></tr> </table> (Date thread and author would all be links)</LI> -<LI> Provide downloadable tar.gz's of the archives</LI> -<LI> When a list switches on archiving, automatically do the archiving regularly (right now you have to install a cron script).</LI> -</UL> -<A NAME=c12><H3>Code cleanup</H3> -<UL> -<LI> Use the re module where regexp and regsub are used.</LI> -<LI> Refine any remaining unqualified exception guards to specify target exceptions, when appropriate.</LI> -<LI> Turn standard mailman exceptions into class exceptions.</LI> -<LI> Seperate edit-options from the subscribe script.</LI> -<LI> Encapsulate all modules into a python package.</LI> -<LI> Remove dead code, etc.</LI> -</UL> -<A NAME=c13><H3>Misc</H3> -<UL> -<LI> Automatically update aliases again?</LI> -<LI> Make the listinfo pages static, and have them regenerate when options are changed, or html is edited.</LI> -<LI> Make it so Mailman can run as a threaded server (this feature should be optional).</LI> -<LI> The threaded server should be able to off its workload to friendly machines if it is overworked (distributed support).</LI> -<LI> Refine locking to lock only necessary sections to get rid of superfluous contention.</LI> -<LI> Implement member profiles, using a class to store name, organization, description, etc, and default option settings. The lists still can have their own data, but the user can set defaults in their profile...</LI> -<LI> Make it so Mailman can be used out of the box for newsgroup gateways.</LI> -</UL> -</BODY></HTML> |