Dear Wiki user, You have subscribed to a wiki page or wiki category on "Httpd Wiki" for change notification.
The "ApacheCon2010Atlanta" page has been changed by RichBowen. http://wiki.apache.org/httpd/ApacheCon2010Atlanta?action=diff&rev1=8&rev2=9 -------------------------------------------------- ---- - ||<)>'''Session Title:'''|| || + ||<)>'''Session Title:'''|| Write a Better FM || - ||<)>'''Speaker:'''|| || + ||<)>'''Speaker:'''|| Rich Bowen || - ||<)>'''Speaker contact info:'''|| || - ||<)>'''Session Abstract:'''|| || - ||<)>'''Speaker bio:'''|| || + ||<)>'''Speaker contact info:'''|| rbowen at apache dot org || + ||<)>'''Session Abstract:'''|| (Quite possibly, this would fit the community track better.) If you've been around Open Source for more than a few minutes, you've had at least one question answered with "go look it up." Or, in the lingo of the technology world, RTFM. The manner in which this was delivered may vary, but the message is the same - it's your job to find your own answers. The trouble is that the Fine Manual, if it even exists, is often inaccurate, brusque, extremely technical, and doesn't actually answer the questions that real people are asking. In this session I'll discuss some of the lessons learned from a decade of end-user support and manual writing. Writing a better manual is harder than just writing out a list of functions and what they do. You also need to know who your audience is, and what questions they're asking. This involves patience, compassion, and a sense of humor, as well as a firm grasp of the rules of grammar. || + ||<)>'''Speaker bio:'''|| Rich Bowen has been involved with the Apache HTTP Server documentation project for about a decade, and has written much of the docs for that product. He's also involved in documentation for PHP and Habari, and has contributed documentation for Perl, Wordpress, and numerous other projects. ||
