Did the mod_usertrack docs.

Would like to do a howto style writeup of the multi-daemon secure
mod_dav configuration.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1027131 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/STATUS b/docs/STATUS
index d85d73c9161ada471f3453a974da686589a8a234..ee57da0c1f11f001f5b3ced977d0187faa506332 100644 (file)
--- a/docs/STATUS
+++ b/docs/STATUS
@@ -138,7 +138,7 @@ To Do List
 
 - How-To style documents for more of the daily tasks
     - Logging, log rotation, and log reporting
-    - ?
+    - Secure mod_dav configuration
 
 - Writing modules - Can we provide a basic intro to writing modules,
   perhaps based around mod_example, or one of the other simple example
@@ -161,12 +161,6 @@ To Do List
   That would be a good place to document logging of cache hit/miss:
   https://issues.apache.org/bugzilla/show_bug.cgi?id=48241#c2
 
-- The mod_usertrack docs should describe what the module does, now,
-  rather than spending so much time comparing it to what a long-gone
-  module, which our readers never used, used to do. Examples would be
-  helpful. Additionally, a significant part of the doc consists of a
-  quoted email message. This seems somewhat unprofessional.
-
 - Is it worth having a doc that discusses recommended (what does this
   mean?) third-party modules like mod_security, mod_php, and so on - the
   things that we all assume everyone uses, but some folks might not know