1 Apache HTTP Server 2.0 Documentation Status File.
3 If you are interested in helping accomplish some of the tasks on this
4 list or otherwise improving the documentation, please join the
5 apache-docs mailing list by mailing to
6 apache-docs-subscribe@apache.org
9 - Each MPM needs to have a documentation file in manual/mod/
10 which lists the directives it provides, and some details
12 Status: Initial outlines done. Much more details need to be
15 - Merging of changes in 1.3.
16 - There have been many changes in the 1.3 docs which haven't
17 been propagated into 2.0.
18 Things which need to be merged:
22 - Joshua thinks this is a good opportunity to think about directory
25 Create manual/FAQ which contains all the manual/misc/FAQ* docs
28 - We could use a list of all the docs that can be axed out of 2.0
29 because they are redundant or irrelevant.
30 Status: Rich <rbowen@rcbowen.com> is going to look at this.
31 Some suggestions on files to axe. Feel free to comment.
32 manual/bind.html (mostly now documented in server-wide.html)
33 manual/cgi-path.html (should be documented in mod_cgi.html instead)
34 manual/multi-logs.html (documented in mod_log_config.html)
35 manual/process-model.html (documented in MPMs, eventually)
36 manual/mod/index-bytype.html
38 - Individual docs will need some cleanup. For example,
39 manual/invoking.html could use a big cleanup with lots of the
40 "this changed in 1.3.10" stuff removed.
44 - The new build process is autoconf based, so manual/install.html
45 will need to be completely rewritten. Someone with enough
46 patience could probably figure out most of the important stuff
48 Status: Ryan's "Building and Installing Apache 2.0" might be
49 a starting place. Rich <rbowen@rcbown.com> is interested
50 in collaborating with someone else on this.
52 - Documentation of new features.
53 - This will probably require more input from new-httpd, since
54 not many people here follow the development process close
55 enough to know what is going on.
56 Status: Ryan has two ApacheToday articles which may be useful
63 - The STATUS Document.
64 - Is this the best organization/format? What else needs to be
65 added? Should this be auto-posted to apache-docs?