docs/master

annotate preface.roff @ 47:eae5e50381ce

Rework in Preface and Intro.
author markus schnalke <meillo@marmaro.de>
date Fri, 18 May 2012 11:21:51 +0200
parents 22ae3981a76b
children 49cf68506b5d
rev   line source
meillo@0 1 .H0 "Preface" no
meillo@0 2
meillo@23 3 .P
meillo@47 4 MH is a set of mail handling tools with a common concept, similar to
meillo@47 5 the Unix toolchest, which is a set of file handling tools with a common
meillo@23 6 concept. nmh is the currently most popular implementation of an
meillo@23 7 MH-like mail handling system.
meillo@47 8 This thesis describes an experimental version of nmh, named \fImmh\fP.
meillo@23 9
meillo@30 10 .U2 "Background to this Thesis
meillo@8 11 .P
meillo@28 12 I have discovered nmh in September 2009. At that time I used to use the
meillo@31 13 mail client \fImutt\fP, like many advanced Unix users do.
meillo@31 14 As I read about nmh, its concepts had convinced me at once.
meillo@31 15 Learning its different model of email handling had been relatively easy,
meillo@31 16 because my starting situation was being convinced of the concepts.
meillo@31 17 The transition from mutt to nmh was similar to
meillo@28 18 managing files in the Unix shell when being used to graphical file
meillo@31 19 managers, or like editing with vi when being used to modeless editors.
meillo@31 20 Such a change is not trivial, but in being convinced by the
meillo@31 21 concepts and by having done similar transitions for file management
meillo@31 22 and editing already, it was not too difficult neither.
meillo@28 23 In contrast, setting up nmh to a convenient state became a tendious task
meillo@23 24 that took several months.
meillo@23 25 .P
meillo@28 26 Once having nmh arranged to a convenient state, I enjoyed using it
meillo@28 27 because of its conceptional elegance and its scripting capabilities.
meillo@23 28 On the other hand, however, it still was
meillo@31 29 inconvenient for handling attachments, non-ASCII character encodings,
meillo@23 30 and similar features of modern emailing.
meillo@31 31 My setup demanded more and more additional configuration and helper scripts
meillo@31 32 to get nmh behave the way I wanted, although my
meillo@31 33 expectations were rather common for modern emailing.
meillo@31 34 In being a computer scientist and programmer,
meillo@31 35 I wanted to improve the situation.
meillo@8 36 .P
meillo@31 37 In Spring 2010, I asked on the \fInmh-workers\fP mailing list for the
meillo@31 38 possibility to offer a Google Summer of Code project.
meillo@23 39 Participating in the development this way appeared attractive to me,
meillo@31 40 as it would have been possible to have the project
meillo@31 41 accepted at university. Although generally the nmh community
meillo@31 42 had been positive on the
meillo@31 43 suggestion, the administrative work had been to much, eventually.
meillo@31 44 But my proposal had activated the nmh community.
meillo@31 45 In the following weeks, goals for nmh's future were discussed.
meillo@31 46 In these discussions, I became involved in the
meillo@34 47 question whether nmh should be an MTA.
meillo@34 48 .[
meillo@34 49 nmh-workers thread mta mua
meillo@34 50 .]
meillo@31 51 In this central point, my opinion differed from the opinion of most others.
meillo@31 52 I argued for the MTA facility of nmh to be removed.
meillo@31 53 Besides the discussions, hardly any real work was done.
meillo@31 54 Being unable to work on nmh in a way that would be
meillo@31 55 accepted as part of my official studies, I needed to choose another project.
meillo@8 56 .P
meillo@23 57 Half a year later, starting in August 2010,
meillo@23 58 I took one semester off to travel through Latin America.
meillo@31 59 Within this time, I had to do practical computer work for three months.
meillo@23 60 This brought me back to nmh.
meillo@23 61 Richard Sandelman, an active nmh user, made it possible for
meillo@23 62 me to work on nmh. Juan Granda, living in Santiago del
meillo@31 63 Estero in Argentina, provided a computer with Internet connection for
meillo@31 64 my work. Thanks to them, I was able to work on nmh during my three-month
meillo@31 65 stay in Argentina.
meillo@31 66 Within this time, I became familiar with nmh's code base and
meillo@31 67 community. I learned how things work. Quickly it became obvious that
meillo@31 68 I wouldn't succeed with my main goal: improving the character
meillo@31 69 encoding handling within the project. One of its ramifications is the
meillo@31 70 missing transfer decoding of quoted text in replies.
meillo@23 71 As this is one of the most intricate parts of the system, the goal
meillo@31 72 was simply set too high. Hence, I dropped the original plan.
meillo@31 73 Instead, I improved the code base as I read through it. I found minor bugs
meillo@31 74 for which I proposed fixes to the community. In the same go, I
meillo@31 75 improved the documentation in minor ways. When I started with
meillo@31 76 larger code changes, I had to discover that the community was reluctant
meillo@31 77 to change. Its wish for compatibility was much stronger than its
meillo@31 78 wish for convenient out-of-the-box setups \(en in contrast to my opinion.
meillo@23 79 This lead to long discussions, again.
meillo@31 80 I came to understand their point of view, but it is different to mine.
meillo@23 81 At the end of my three-month project, I had become familiar with
meillo@31 82 nmh's code base and community. I had improved the project in minor ways,
meillo@31 83 and I still was convinced that I wanted to go on to do so.
meillo@23 84 .P
meillo@23 85 Another half a year later, the end of my studies came within reach.
meillo@23 86 I needed a topic for my master's thesis.
meillo@23 87 There was no question: I wanted to work on nmh.
meillo@23 88 But well, not exactly on nmh,
meillo@8 89 because I had accepted that the nmh community has different goals
meillo@31 90 than I have. This would result in much discussion and thus little progress.
meillo@23 91 After careful thought, I decided to start an experimental version of nmh.
meillo@31 92 I wanted to implement my own ideas of how an MH-like system should look like.
meillo@31 93 I wanted to see where that would lead to.
meillo@31 94 I wanted to create a usable alternative version to be compared with
meillo@31 95 the present state of nmh.
meillo@31 96 My work should be proved successful or failed.
meillo@31 97 The nmh project would not be hurt by my work, but
meillo@31 98 it would profit from my experiences.
meillo@28 99
meillo@30 100 .U2 "Focus of this Document
meillo@8 101 .P
meillo@47 102 This document describes my work on mmh.
meillo@47 103 It explains the changes to nmh, with focus on their reasons.
meillo@31 104 It discusses technical, historical, social and philosophical considerations.
meillo@31 105 On the technical side, this document
meillo@31 106 explains how an existing project was stream-lined by removing rough edges
meillo@31 107 and exploiting the central concepts better.
meillo@31 108 On the historical
meillo@31 109 side, changes through time in the use cases and the email features,
meillo@31 110 as well as the reactions to them, are discussed.
meillo@31 111 Socially, this document describes the effects
meillo@28 112 and experiences of a newcomer with revolutionary aims entering an old
meillo@31 113 and matured software projects.
meillo@31 114 Finally, philosophical thoughts on style, mainly based to the Unix philosophy,
meillo@31 115 are present throughout the discussions.
meillo@23 116 .P
meillo@31 117 This document is written for the community around MH-like mail systems,
meillo@31 118 including developers and users.
meillo@31 119 First of all, the document shall explain the design goals and
meillo@31 120 implementation decisions for mmh. But as well, it shall clarify my
meillo@30 121 personal perception of the
meillo@31 122 concepts of MH and Unix, and explain my therefrom resulting point of view.
meillo@31 123 Despite the focus on MH-like systems, this document may be worthwhile
meillo@31 124 to anyone interested in the Unix philosophy and anyone in contact to
meillo@31 125 old software projects, be it code or community-related.
meillo@28 126 .P
meillo@30 127 The reader is expected to have good knowledge of Unix, C and emailing.
meillo@30 128 Good Unix shell
meillo@28 129 knowledge, including shell scripting, is required. MH relies fundamentally
meillo@28 130 on the shell. Without the power of the shell, MH becomes a motorbike
meillo@30 131 without winding roads: boring.
meillo@31 132 Introductions to Unix and its shell can be found in ``The UNIX Programming
meillo@37 133 Environment'' by Kernighan and Pike
meillo@37 134 .[
meillo@37 135 kernighan pike unix prog env
meillo@37 136 .]
meillo@37 137 or ``The UNIX System'' by Bourne.
meillo@37 138 .[
meillo@37 139 bourne unix system
meillo@37 140 .]
meillo@28 141 The reader is
meillo@28 142 expected to be familiar with the C programming language, although the
meillo@30 143 document should be understandable without knowledge of C, too.
meillo@37 144 ``The C Programming Language'' by Kernighan and Ritchie
meillo@37 145 .[
meillo@37 146 kernighan ritchie c prog lang
meillo@37 147 .]
meillo@37 148 is the definitive guide to C.
meillo@28 149 Some book about system-level C programming is worthwile additional
meillo@28 150 literature. Rochkind and Curry have written such books.
meillo@37 151 .[
meillo@37 152 rochkind advanced unix prog
meillo@37 153 .]
meillo@37 154 .[
meillo@37 155 curry system prog
meillo@37 156 .]
meillo@31 157 As large parts of the code are old, old books are likely more helpful
meillo@31 158 to understanding.
meillo@28 159 The format of email messages as well as the structure of email transfer
meillo@28 160 systems should be familiar to the reader, at least on a basic level.
meillo@31 161 It's advisable to have at least cross-read the RFCs 821 and 822.
meillo@31 162 Further more, basic understanding of MIME is good to have.
meillo@31 163 The Wikipedia provides good introduction-level information to email.
meillo@28 164 Frequent references to the Unix philosophy will be made.
meillo@34 165 Gancarz had tried to sum the philosophy up in his book
meillo@34 166 ``The UNIX Philosophy''.
meillo@34 167 .[
meillo@34 168 gancarz unix phil
meillo@34 169 .]
meillo@47 170 Even better, though less concrete, are ``The UNIX Programming Environment''
meillo@34 171 .[
meillo@34 172 kernighan pike unix prog env
meillo@34 173 .]
meillo@34 174 and ``The Practice of Programming''
meillo@34 175 .[
meillo@34 176 kernighan pike practice of prog
meillo@34 177 .]
meillo@34 178 by Kernighan and Pike.
meillo@34 179 The term paper ``Why the Unix Philosophy still matters''
meillo@34 180 .[
meillo@34 181 why unix phil still matters schnalke
meillo@34 182 .]
meillo@34 183 by myself
meillo@28 184 provides an overview on the topic, including a case study of MH.
meillo@30 185 Although a brief introduction to MH is provided in Chapter 1, the reader
meillo@30 186 is encouraged to have a look at the \fIMH Book\fP by Jerry Peek.
meillo@34 187 .[
meillo@34 188 peek mh
meillo@34 189 .]
meillo@30 190 It is the definitive guide to MH and nmh.
meillo@31 191 The current version is available freely on the Internet.
meillo@30 192 .P
meillo@30 193 This document is neither a user's tutorial to mmh nor an introduction
meillo@31 194 to any of the topics covered. It discusses Unix, email
meillo@30 195 and system design on an advanced level.
meillo@30 196 However, as knowledge of the fundamental concepts is the most valuable
meillo@31 197 information a user can aquire about some program or software system,
meillo@31 198 this document might be worth a read for non-developers as well.
meillo@8 199
meillo@8 200
meillo@28 201 .U2 "Organization
meillo@0 202 .P
meillo@28 203 Which font for what use.
meillo@28 204 Meaning of `foo(1)'.
meillo@28 205 RFCs.
meillo@28 206 .P
meillo@28 207 This thesis is devided into XXX chapters, ...
meillo@24 208 .P
meillo@24 209 .I Chapter 1
meillo@24 210 introduces ...
meillo@24 211 .P
meillo@24 212 .I Chapter 2
meillo@24 213 describes ...
meillo@24 214 .P
meillo@24 215 .I Chapter 3
meillo@24 216 covers ...
meillo@24 217
meillo@23 218
meillo@28 219 .U2 "Acknowledgments
meillo@23 220 .P
meillo@24 221 To be written at the very end.