docs/master

annotate preface.roff @ 66:4c9f4d05d90e

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