1.1 --- a/thesis/tex/7-Summary.tex	Tue Jan 27 11:18:30 2009 +0100
     1.2 +++ b/thesis/tex/7-Summary.tex	Tue Jan 27 12:10:40 2009 +0100
     1.3 @@ -1,11 +1,33 @@
     1.4  \chapter{Summary}
     1.5  
     1.6 -<< what was done, what was achieved >>
     1.7 +This thesis is a comprehensive analysis of \masqmail. It followed a clear structure from the present to the future, from the problems to the requirements to proposed solutions, and from the general to the special.
     1.8  
     1.9 +The reasons why it is worth to restart development on the project and the problems to solve were identified in the beginning. The the current and future market for electronic communication and email was analysed to show that it is future-proof and to spot future needs. Afterwards the different types of \MTA{}s were classified and the most important alternatives to \masqmail\ were presented and compared.
    1.10  
    1.11 -<< plans to get masqmail more popular again (if that is the goal) --- More users --- how to advertise masqmail >>
    1.12 +In the second half of the thesis, \masqmail\ stood in the focus. First the goal to reach with further development was defined, then the requirements to reach it were identified. The existing source code was compared against them to see which requirements are already fulfilled. The pending work tasks were ranked by their importance and the amount of work they involve, to receive a list of tasks ordered by the focus they should receive.
    1.13  
    1.14 +The possible strategies to control further development---improve existing code or redesign and rewrite---were compared against each other on basis of the pending work tasks. They were additionally discussed by regarding various other influences. The final decision is a twofold aim: First improve the existing code to keep it usable for the next time. Second, design a new version of \masqmail\ with respect for the modern goals for \MTA{}s that were identified throughout the thesis.
    1.15  
    1.16 +In the end more concrete plans for the improvements of the existing code were made and a suggestion for a new design for \masqmail\ is presented. The descripton of this new design leaves quite a few questions open; it is more a discussion on the topic with suggested solutions. Covering such a topic throughout would take at least a second diploma thesis or a master's thesis. More information needs to be collected and further studies of the situations in existing \MTA{}s need to be made.
    1.17  
    1.18 -<< Further life of the project >>
    1.19  
    1.20 +\subsubsection*{Outlook}
    1.21 +
    1.22 +Writing this thesis is not the end of my work on \masqmail\ but the beginning. The next important step is creating a community of people that are interested in reviving \masqmail's development. Then comes implementing the identified tasks together with this group of volunteers, and afterwards designing \masqmail\ new.
    1.23 +
    1.24 +Of course there are known, but unfixed, bugs in \masqmail. Those need to be closed.
    1.25 +
    1.26 +Documentation and ``marketing'' is important too. Especially end user documentation is needed and people who help to distribute the knowledge of the existence and the advantages of \masqmail.
    1.27 +
    1.28 +\masqmail\ is valuable software---this thesis is a first effort to revive it---it will not be the last.
    1.29 +
    1.30 +
    1.31 +
    1.32 +
    1.33 +
    1.34 +
    1.35 +
    1.36 +%``This is the Unix philosophy: Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface.'' Doug McIlroy (quoted in Peter H. Salus. A Quarter-Century of Unix. Addison-Wesley. 1994. ISBN 0-201-54777-5.)
    1.37 +
    1.38 +
    1.39 +