STATUS revision 1df5892d36744c90da41490b57f824e75dff8f8e
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobsApache HTTP Server 2.0 Documentation Status File.
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobsLast modified: $Date: 2001/04/27 11:42:11 $
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobsIf you are interested in helping accomplish some of the tasks on this
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobslist or otherwise improving the documentation, please join the
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobsapache-docs mailing list by mailing to
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobsapache-docs-subscribe@apache.org
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs- man pages
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs - Some of the man pages need to be updated for 2.0. At least
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs the httpd man page appears to be outdated, and perhaps other.
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs After this is done, the manual/programs/ versions can be
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs regenerated.
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs- XHTML conversion
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs Status: James A Sutherland <jas88@cam.ac.uk> was going
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs to spearhead this, but we haven't heard anything
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs lately. Some work is still needed
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs to determine what the SSIs should look like.
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs- MPM documentation
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs - Each MPM needs to have a documentation file in manual/mod/
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs which lists the directives it provides, and some details
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs about its operation.
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs Status: Initial outlines done. Much more details need to be
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs filled in.
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs - Non unix/windows MPMs still need to be completed.
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs - perchild MPM needs some docs.
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs- Merging of changes in 1.3.
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs - There have been many changes in the 1.3 docs which haven't
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs been propagated into 2.0.
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs Things which need to be merged: ???
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs- Cleaning.
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs - We could use a list of all the docs that can be axed out of 2.0
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs because they are redundant or irrelevant.
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs Status:
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs Some suggestions on files to axe. Feel free to comment.
4e9cfc9a015e8ca7d41f7d018c74dc8a692305b3jacobs manual/cgi-path.html (should be documented in mod_cgi.html instead)
manual/process-model.html (documented in MPMs, eventually)
platform/perf-* (are these relevant anymore?)
- Individual docs will need some cleanup.
Status: What docs still need to be touched here?
- invoking.html has had a first-pass cleaning done.
- misc/perf-tuning.html - needs major rewrite for 2.0
- misc/FAQ.html - some old questions could be remove
- is a new format in order?
- misc/tutorials.html - mostly not relevant to 2.0
- misc/stopping.html
- dso.html
- misc/rewriteguide.html - needs cleaning in 1.3 and 2.0
- misc/known_client_problems.html - mostly ancient
- howto/* - some syntax has changed in 2.0 due to
filtering and mod_cgid
- New build process.
- The new build process is autoconf based, so manual/install.html
will need to be completely rewritten. Someone with enough
patience could probably figure out most of the important stuff
by trial and error.
Status: Ryan's "Building and Installing Apache 2.0" might be
a starting place.
- Documentation of new features.
- This will probably require more input from new-httpd, since
not many people here follow the development process close
enough to know what is going on.
Status: Ryan has two ApacheToday articles which may be useful
for this.
New features which need documentation:
- filters !!!
- Translations
We appear to have people working on translation into the following
languages. These may just be the 'it worked' page, but if so
the authors of those should perhaps be contacted to help do the
rest.. :-) Note that this list is NOT identical to that for the
1.3 documentation project..!
- Catalan (.ca)
- Czech [?] (.cz)
- German (.de)
- Danish (.dk)
- ? (.ee)
- Greek (.el)
- Spanish (.es)
- Estonian (.et)
- French (.fr)
- Hebrew (.he.iso8859-8)
- Italian (.it)
- Japanese (.ja.iso2022-jp, .ja.jis)
- Korean (.kr.iso2022-kr, .kt.iso-kr)
- ? (.ltz)
- ? (.lu)
- Dutch (.nl)
- Norwegian (.no)
- Polish (.po.iso-pl)
- Portuguese (.pt)
- Portuguese [Brasilian] (.pt-br)
- Russian (.ru.cp-1251, .ru.cp866, .ru.iso-ru, .ru.koi8-r, .ru.ucs[248])
- Swedish (.se)
- Twi (.tw, .tw.big5)
(is that supposed to be Chinese/Taiwanese? Because if so, it is using
the code reserved for Twi..)