Changes between Version 18 and Version 19 of MichaelRay


Ignore:
Timestamp:
Nov 4, 2013 7:05:48 AM (4 years ago)
Author:
MichaelRay
Comment:

S&W

Legend:

Unmodified
Added
Removed
Modified
  • MichaelRay

    v18 v19  
    22Problems / Ideas:
    33
     4* summary
     5* illustrations
    46* have pointers to the manual.txt for related wiki pages (wiki
    57 * wiki page becomes illustrative extension and/or summary
     
    79 * find documentation discrepancies between them (update)
    810 * use anchors to improve long page navigation
    9  * can the title index macro be limited to the current page?
     11 * use the title index macro be limited to the current page
    1012
    11 * two documentation tracks
    12  * immediate problem fix (MuttFAQ)
    13  * advanced feature (failure/"pre-bug report" req. thorough search)
    14  * essentially "no expectation of reading the manual.txt vs. expectation that you do"
    15  * precedence: common problems MuttGuide) vs. advanced problems (Debug)
    16 * hooks (documentation inconsistency?)
    17 * user interface optimizatoin
    18  * optimal colorization for TUI (general problem)
    19  * "should" features -> fucking html mail, image links, javascript required destinations
    20   * lynx v elinks v links v ff
    21 * flea / bugs.guug.de (broken) ( bug reporting)
    22  * bugs.mutt.org (old references)?
    23 * minimal documentation for usability
    24   * few people going to read an entire manual just to use a mail client
    25    * compare to alternatives
    26   * common end-user approach problem -> search around specific problem -> solution -> abandon documentation
    27   * other (sites) pages around specific problems (gmail/gpg) may get more hits
    28    * better readability
    29    * working examples
    30    * "fresher" examples
    3113* "high probability" documentation needs
    32  * gpg
    33   * strengths: gpg support excellent
    34   * gpg is non-trivial for many end-users (failed adoption/client switching)?
    35    * need to remove / explain gpg concepts vis-a-vis mutt gpg (probably pre-existing docs do a better job)
    36  * use of external mail providers: http://email.about.com/od/freeemailreviews/tp/free_email.htm
    37    * gmail
    38      * imap http://email.about.com/od/accessinggmail/f/Gmail_IMAP_Settings.htm
    39    * yahoo
    40      * http://help.yahoo.com/kb/index?locale=en_US&y=PROD_MAIL_MOBILE&page=content&id=SLN4075
    41    * hushmail / secure email provider integration (hushmail has paid imap)?
    42      * imap https://help.hushmail.com/categories/1051-POP-IMAP
    43    * http://darkmail.info/
    44  * folders
    45  * mail management (high volume mailing list)
    46  * basic configuration (From)
    47  * multiple account management
    48  * mail saving / sorting
    49  * mail box search (strong google feature)
    50  * basic navigation
    51  * alternate editor configuration (default to 'easy' editor -> vi-> mg ->)
    52  * simple default muttcfg with commented comment options?
    53  * aliases (abook integration)
    54  * imap/pop
    55 
    56 * updated / current compilation instructions for each platform
    57  (binary vs. source)
    58  * SRC: !Arch/Gentoo/Slack/LFS ( emerge / pacman / un )
    59    * arch https://bbs.archlinux.org/viewtopic.php?pid=1259651
    60    * lfs http://www.linuxfromscratch.org/blfs/view/svn/basicnet/mutt.html
    61    * http://www.slackwiki.com/Mutt (pre-installed)
    62  * BSD !open/free/netbsd/macOS !OpenSolaris? (ports / pkgadd dependencies)
    63  * RH redhat/centos, openmandriva (yum dependencies)
    64  * DEB: debian/ubuntu, derivaties (apt-get/dpkg dependencies)
    65  * (yast?)
    66  * common problems / solutions (MuttFAQ)
    67  * version problems around distributions vs. mutt reqs?
    68 
    69 * mutt strengths
    70  * great cross platform support
    71  * great protocol support (w/ modifications)
    72  * used by many high profile users
    73  * generally powerful
    74  * relatively simple for most basic functions
    75  * flexible interactive v. non-interactive
    76  * relatively few alternatives
    77    * TUI alternative comparisons
    78  * favored by advanced users
    79 
    80 * mutt weaknesses
    81  * documentation
    82   * "wall of documentation" problem (same as Wikipedia)
    83  * release schedule /updates? (perception?)
    84   * 'dev' version vs. stable (?)
    85  * high learning curve for many (perhaps common) features
    86  * initial installations may not have working defaults (distribution)
    87  * mail (generally) is non-"straightforward" - networking component
    88  * integration difficulties?
    89  * provide clear, simple default configs (MuttGuide)?
    90  * imap/ldap/exchange (corporate environments/remote users)?
    9114
    9215* phone / tablet platforms? iphone / android (juicessh => shell)