1.1 --- a/summary.roff	Mon Jul 09 22:32:24 2012 +0200
     1.2 +++ b/summary.roff	Mon Jul 09 23:42:59 2012 +0200
     1.3 @@ -24,10 +24,10 @@
     1.4  developing and using, without lacking important functionality.
     1.5  
     1.6  
     1.7 -.U2 "Work Left to Do
     1.8 +.U2 "Outlook
     1.9  .P
    1.10  The work done during the project is not finished.
    1.11 -Several tasks are left to do, mainly the MIME integration.
    1.12 +Several tasks are left to do.
    1.13  .P
    1.14  MIME handling is the most complex part of mmh and it requires
    1.15  general rework.
    1.16 @@ -54,7 +54,7 @@
    1.17  .Hd Subject
    1.18  remain unsolved.
    1.19  .P
    1.20 -Besides MIME-related tasks, some tools were not worked on yet.
    1.21 +Some of mmh's tools were hardly touched during my work.
    1.22  Among them are
    1.23  .Pn dist ,
    1.24  .Pn rcvdist ,
    1.25 @@ -62,19 +62,30 @@
    1.26  .Pn pick ,
    1.27  and
    1.28  .Pn sortm .
    1.29 -Concerning
    1.30 +Related to
    1.31  .Pn sortm ,
    1.32  a threaded message view is completely missing to mmh, yet.
    1.33  .Pn pick
    1.34 -could profit from message indexing.
    1.35 -No research was performed in this field.
    1.36 +could be enhanced by message indexing.
    1.37 +These fields are worthwhile for research.
    1.38  .P
    1.39  The features most often asked for are Maildir and IMAP support.
    1.40  Yet, both of them collide with MH in the same fundamental way as
    1.41  different filesystem approaches would collide with Unix.
    1.42 -Nevertheless, a storage back-end abstraction layer could provide
    1.43 -a mapping from such back-ends to the MH storage format.
    1.44 +Nevertheless, an abstraction layer could provide a mapping from such
    1.45 +storage back-ends to the MH storage format.
    1.46 +Or the mmh toolchest could be reworked to operate on a generic back-end,
    1.47 +making the MH storage format only one of many possible back-ends.
    1.48  Research in this area is highly appreciated.
    1.49 +.\" XXX targeting the right problems?!
    1.50 +.P
    1.51 +Nmh has a testing framework that supported the developers by detecting
    1.52 +several subtle bugs.
    1.53 +All refactoring in mmh had been done without the safety net of a test
    1.54 +framework.
    1.55 +Hence, experience warns that the probability for subtle bugs lurking
    1.56 +in the code base is high.
    1.57 +Nmh's test framework should be adjusted to mmh and extended.
    1.58  
    1.59  
    1.60  .U2 "Relationship to nmh
    1.61 @@ -85,6 +96,7 @@
    1.62  discussions for each step I liked to take,
    1.63  I started to create an experimental version to convicce by demonstration
    1.64  of the result.
    1.65 +.\" behind closed doors; talks I've given
    1.66  My worked on mmh was independent of the nmh community.
    1.67  This enabled me to follow my vision straightly and thus produce
    1.68  a result of greater pureness.