Commit 1c81d868 authored by Joshua Slive's avatar Joshua Slive
Browse files

Vancouver is rainy and cold today. Better stay indoors.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@87714 13f79535-47bb-0310-9956-ffa450edef68
parent a0704171
Loading
Loading
Loading
Loading
+11 −10
Original line number Diff line number Diff line
@@ -5,9 +5,16 @@ list or otherwise improving the documentation, please join the
apache-docs mailing list by mailing to 
apache-docs-subscribe@apache.org

- man pages
    - Some of the man pages need to be updated for 2.0.  At least
      the httpd man page appears to be outdated, and perhaps other.
      After this is done, the manual/programs/ versions can be
      regenerated.

- XHTML conversion
        Status: James A Sutherland <jas88@cam.ac.uk> was going
                to spearhead this.  Some work is still needed
                to spearhead this, but we haven't heard anything
                lately.  Some work is still needed
                to determine what the SSIs should look like.

- MPM documentation
@@ -22,12 +29,12 @@ apache-docs-subscribe@apache.org
- Merging of changes in 1.3.
   - There have been many changes in the 1.3 docs which haven't
     been propagated into 2.0.
     Things which need to be merged:
     Things which need to be merged: ???

- Cleaning.
   - We could use a list of all the docs that can be axed out of 2.0
     because they are redundant or irrelevant.
        Status: Rich <rbowen@rcbowen.com> is going to look at this.
        Status:
	Some suggestions on files to axe.  Feel free to comment.
          manual/cgi-path.html (should be documented in mod_cgi.html instead)
          manual/process-model.html (documented in MPMs, eventually)
@@ -54,8 +61,7 @@ apache-docs-subscribe@apache.org
     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.  Rich <rbowen@rcbown.com> is interested
                in collaborating with someone else on this.
                a starting place.  

- Documentation of new features.
   - This will probably require more input from new-httpd, since
@@ -68,8 +74,3 @@ apache-docs-subscribe@apache.org

- Translations
        Status: ???


- The STATUS Document.
   - Is this the best organization/format?  What else needs to be
     added?  Should this be auto-posted to apache-docs?