Acmemail Timeline
===========================================================================

The following is a rough timeline for the next development (2.3.x), 
stable (2.4.x), and development (2.5.x) versions of acmemail.

You will notice that everything is basically separated into three different stages:
 1. Do things that are almost done or are fairly simple to do
 2. Implement features that others have put into their own versions of 
    acmemail 2.2
 3. Do other things that will require a bit of thought, research, and design 
    to implement

Things can of course be moved up if people step forward with code.  So far, since 
Leon Brocard gave the project to the acmemail community, few have done so (other 
than Peter Watkins and Ron Andrews) :-)

The latest version of this document is currently available at http://acmemail.sf.net/timeline.txt

Wim Kerkhoff <wim@merilus.com>
March 31, 2001

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Acmemail 2.3.0 (development series) [Mid-June]:
 do/finish/test simple things as follows:
 - developer testing of all existing features (MOSTLY DONE)
 - nested folders using MH or MBOX under UW IMAP and Cyrus folders (DONE)
 - sent mail folder (DONE)
 - an installer, that will check perl modules, configuration, database access, 
   etc. OR a CPAN type installation (?)
 - update documention to reflect all the new things
 - improved handling of multipart/related messages (already better)
 - judicious use of JavaScript if it's available but remains fully functional 
   if it's not
 - ensure all code uses Acmemail::Config for configuration. No hardcoded values.
 - ensure theme support has been finished (DONE, except for threading)
 - ensure all screens are printed using the templating system (DONE (except threading))

Acmemail 2.3.1 [End of June]:
 fixes from 2.3.0
 - fixes to documentation
 - make images that use <img src="cid:something.gif"> syntax work

Acmemail 2.3.2 [End of June]::
 implement things that Wim has done in his hacked up version as follows:
 - moving messages between mailboxes 
 - user level configuration:
   * block signatures 
   * S/MIME verification/signing/encryption/decryption 
   * poll times for mail index 
   * drafts folder 
   * sent mail folder 
 - address books using David Leigh's AddressBook modules (perl-abook.sf.net)
 - fix for Bcc problems (need bug reports)
 - poll times for mail index
 - drafts folder 

Acmemail 2.3.3 [End of June]:
 finish things that have kinda been started, but still need a load of work
 - user definable message filtering rules using procmail [1/2 done]
 - finish message threading [11/16ths done]
 - frames

Acmemail 2.3.4 [End of June]:
 - importing/exporting of address books between various formats 
 - option for full header display (easy to do with themes)

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Acmemail 2.4.0 (Stable series) [Beginning of July]:
 - update documentation / website / screenshots
 - fork new tree in CVS for new development
 - A printer-friendly viewing option via themes
 - create new themes
 - improve speed
 - improve MIME parsing
 - test different session and address book types

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Acmemail 2.5.0 (Development series):
 start thinking about, designing, and implementing other things, such as:
 - next/previous buttons from within a message
 - the whole notion of subscribing to IMAP directories?
 - entire message database search (eg IMAP search)
 - web frontend to system wide settings?
 - handling of PGP messages (signature verification at least)
 - move configuration to flat text file that can be easily read and written by 
   configuration scripts?
 - handling of uuencoded files as attachments (possibly also MS tnef)
 - multiple attachments (if we ever figure out a decent way of doing it :/ )
 - spell checking
 - sortable message index 
 - pick list of recent addresses
 - possibly syslog error logging (ick)
 - inline conversion of hard documents to a viewable format (eg MS Word)
 - displaying (and possibly showing) X-Face headers
 - the summary view should be customisable (huh??)
 - default quotas (size of messages / attachments)
 - Possibly option to export a folder or message in MBOX format
 - add administrator-definable extra message headers
 - add administrator-definable taglines on messages
 - if display gets abstracted enough then maybe something like a GTK frontend