httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: httpd-2.0/docs STATUS
Date Sat, 28 Jun 2003 18:31:59 GMT
slive       2003/06/28 11:31:59

  Modified:    docs     STATUS
  The decision on the FAQ is basically made: we'll slowly build a new one
  for 2.0.
  With regard to more colaborative docs, I'm still open to discussion.
  Also: remind about the crappy ScriptInterpreterSource doc.  As someone
  who rarely runs apache under windows, I don't know enough about it to fix
  it myself.
  Revision  Changes    Path
  1.90      +5 -25     httpd-2.0/docs/STATUS
  Index: STATUS
  RCS file: /home/cvs/httpd-2.0/docs/STATUS,v
  retrieving revision 1.89
  retrieving revision 1.90
  diff -u -d -b -u -r1.89 -r1.90
  --- STATUS	27 Jun 2003 04:42:58 -0000	1.89
  +++ STATUS	28 Jun 2003 18:31:58 -0000	1.90
  @@ -9,29 +9,6 @@
   Decisions pending
  -- Figure out what to do about the 2.0 FAQ
  -    - Copy important stuff from 1.3?
  -    - Some kind of XML?
  -    - Perhaps we can use the newly created Wiki for this. (SubWiki,
  -      with the possibility to get nice commit mails.)
  -       nd: someone should try to convince me, what the heck is
  -           so cool with wikis
  -       erik: it lowers the entry barrier and therefore users are able
  -             to contribute without all the build hassles (see PHP site)
  -       nd: yes, good bad example. The PHP docs would mostly be
  -           better without these comments. I don't want to censor
  -           the entries, but also don't want to leave them without
  -           control. IMHO it's better to incorporate changes into the
  -           static docs. We need some better way of feedback, anyway.
  -       erik: yes, the plan could be to have the wiki as some sort of
  -             scratch_pad (clearly stated on the relevant pages) and
  -             finally incorporate the useful info in it into the static
  -             documentation
  -       jsl: +1 with nd on Wikis, especially regarding the PHP site.  Why
  -            not (continue to) use Bugzilla?  Filters out people without
  -            a general clue (ergo most probably stupid submissions
  -            anyhow), has assignees, tracking/history etc.
   Things That Need Fixing
  @@ -42,6 +19,9 @@
         registry entries etc) (PR 10154)
       - FAQ! UTF-8 config and URL encoding for non-ascii characters.
  +- ScriptInterpreterSource directive is poorly documented.  In particular,
  +  registry-strict is pretty-much useless without more info.
   - New Auth system
       - Much clean-up and enhancement of aaa howto
       - Independent note on how to upgrade to new auth system
  @@ -113,7 +93,7 @@
       a similar effect.
   * Autogeneration of PDF
  -  - Andre is working on this, Erik volunteers to help out
  +  - See manual/style/latex/TODO
   * Improving the documentation of the documentations' build system
     itself (requirements, procedures)

View raw message