docs/master

changeset 192:68980dab3236

Rework of the Summary.
author markus schnalke <meillo@marmaro.de>
date Wed, 11 Jul 2012 20:22:01 +0200
parents fe0e605c073b
children 74a76ad00ba0
files input/sloc.grap summary.roff
diffstat 2 files changed, 36 insertions(+), 45 deletions(-) [+]
line diff
     1.1 --- a/input/sloc.grap	Wed Jul 11 18:37:23 2012 +0200
     1.2 +++ b/input/sloc.grap	Wed Jul 11 20:22:01 2012 +0200
     1.3 @@ -2,7 +2,7 @@
     1.4  frame invis bot solid left solid
     1.5  label left "lines" "of" "code" left .3
     1.6  label bot "changesets in the version control system in linear scale" \
     1.7 -		"(inner ticks are turns of the year)" down .1
     1.8 +		"(the inner ticks are turns of the year)" down .1
     1.9  coord x 0,1300 y 0,60000
    1.10  ticks bot out at 0 "1999-04", 697 "2011-09", 1212 "2012-07"
    1.11  ticks bot in at 79 "", \
     2.1 --- a/summary.roff	Wed Jul 11 18:37:23 2012 +0200
     2.2 +++ b/summary.roff	Wed Jul 11 20:22:01 2012 +0200
     2.3 @@ -32,9 +32,6 @@
     2.4  
     2.5  .U2 "Outlook
     2.6  .P
     2.7 -The work on mmh is not finished.
     2.8 -Several tasks are left to do.
     2.9 -.P
    2.10  MIME handling is the most complex part of mmh and the one with the
    2.11  highest potential for improvements.
    2.12  The changes already accomplished so far build upon the existing structure,
    2.13 @@ -88,58 +85,52 @@
    2.14  .U2 "Relationship to nmh
    2.15  .P
    2.16  The mmh project started as an experimental version of nmh because the
    2.17 -nmh community did not welcome my changes in the mainline version.
    2.18 -To not slow down my work by the need to convince the community in
    2.19 -discussions for each step I liked to take,
    2.20 -I started to create an experimental version to convicce by demonstration
    2.21 -of the result.
    2.22 -.\" behind closed doors; talks I've given
    2.23 -My work on mmh was independent of the nmh community. .\" XXX clarify
    2.24 -.\" XXX straight?
    2.25 -This enabled me to follow my vision straightforwardly and thus produce
    2.26 -a result of greater pureness.
    2.27 +nmh community did not welcome my plans and visions.
    2.28 +The need to convincing the community of every change I liked to
    2.29 +undertake would have slowed down my work too much.
    2.30 +Hence, I created this experimental version to convince by demonstration.
    2.31 +.\" This enabled me to follow my vision straightforwardly and thus produce
    2.32 +.\" a result of greater pureness.
    2.33  .P
    2.34 -Mmh shall be considered as an inspiration for the future development of nmh.
    2.35 -It shall identify weak parts of nmh and suggest possible
    2.36 -improvements by change.
    2.37 -It shall present a lean appearance that is simpler to understand
    2.38 -and work with for developers and users.
    2.39 -By all means, my work on mmh shall improve nmh somehow.
    2.40 -Improving nmh directly in the way I wanted was impossible
    2.41 -due to personal and community-related circumstances.
    2.42 -The mmh project is my way to offer my gifts though.
    2.43 -.\" XXX zweimal ``my way''
    2.44 +While I worked on mmh, nmh's community became very active as well.
    2.45 +Although we both worked on the same code base, there was no collaberation.
    2.46 +This, I must admit, was my failure because I kept my work hidden
    2.47 +from the nmh community.
    2.48 +The reasons are personal and community-related.
    2.49 +I am sorry for that and I like to improve in the future.
    2.50 +Nonetheless, my work was in the public of the regional computer community.
    2.51 +I discussed with friends and presented my work in two video-recorded
    2.52 +lectures.
    2.53 +.[
    2.54 +chaosseminar ccc ulm mmh
    2.55 +.]
    2.56 +.[
    2.57 +gpn entropia mmh
    2.58 +.]
    2.59 +First users appeared and provided feedback.
    2.60  .P
    2.61 -.\" XXX
    2.62 -During my work on mmh, the community of nmh suddenly became very active.
    2.63 -In parallel to my work on mmh, they have worked on nmh. \" XXX rewrite
    2.64 -There was no collaberation in our work, except that I have pulled some
    2.65 -changes from nmh to mmh.
    2.66 -Our work was motivated partly by similar and partly by different aims.
    2.67 -Although some changes are common among both projects,
    2.68 -fundamental differences exist.
    2.69 -My experimental version thus more and more felt like being a fork.
    2.70 -I am still undecided how I like to treat it.
    2.71 +Over time, I had to realize that, although nmh and mmh have much
    2.72 +in common, the projects target different goals.
    2.73 +I am still undecided how to handle it, but my experimental version
    2.74 +more and more feels like being a fork.
    2.75 +As I am strongly convinced that my decisions taken during the
    2.76 +development of mmh are good ones, regarding my goals,
    2.77 +I like to push the project farther in this direction.
    2.78 +
    2.79 +.\" I shall follow my vision straightforwardly and thus produce
    2.80 +.\" a result of greatest pureness.
    2.81 +
    2.82  .P
    2.83 -I am strongly convinced that the decisions taken for the
    2.84 -development of mmh were good ones regarding my goals,
    2.85 -and I like to push the project farther in this direction.
    2.86 +.\" The mmh project and this document are my way to do so.
    2.87  
    2.88  
    2.89  .ig
    2.90 +
    2.91  .U2 "Weaknesses of My Work
    2.92  .P
    2.93  not targeting on the right problems (maildir, imap)
    2.94  
    2.95  .P
    2.96 -refactoring requires testing, automated testing
    2.97 -
    2.98 -.P
    2.99 -communication with nmh.
   2.100 -worked behind closed doors, but no:
   2.101 -talks I've given
   2.102 -
   2.103 -.P
   2.104  focus on myself.
   2.105  But: If good for me then also good for others.
   2.106  ..