> - MPM documentation > - each MPM needs to have a documentation file in manual/mod/ > (or perhaps manual/mod/mpm) > which lists the directives it provides, and some details > about its operation.
I can get a basic definition of each MPM's operation to whoever wants it. I have the file written, I just have to dig it up. I'll try to find it and post it tomorrow sometime. > - 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. I have been meaning to commit up my apachetoday articles as soon as they get out of the 90 restricted time period, and this is as good a reason as any to actually get off my butt and do it. I can see one problem, and that is that the articles aren't usually written like the rest of the documentation. I have three articles that I want to give back to the ASF. 1) An Introduction to Apache 2.0 2) Looking at Apache 2.0 Alpha 4 3) Building and Installing Apache 2.0 I will warn you that I was using StarOffice to create the docs until my September article, so the HTML is horrible and messy. Should I post those to a web site or find a good place and commit them? I would REALLY prefer it if somebody would go in and make my articles look like our docs a bit more. Just tell me the easiest way to proceed. > I wonder if we should have a doc like this committed to each > repository so that we can keep track of things that need > to be done (like the STATUS file in the source distribution). +1 Ryan _______________________________________________________________________________ Ryan Bloom [EMAIL PROTECTED] 406 29th St. San Francisco, CA 94131 -------------------------------------------------------------------------------
