|
|||||||||||
|
Re: Apache Doc Project
From: Michele Petrovsky <petrovsk(at)voicenet.com>
Date: Wed Nov 04 1998 - 10:22:21 EST
>Don't flame me, but what I have in mind is a far more drastic move toward an
Far from flaming - I think everything you're suggesting here is right on. >Call it Project Guidelines.
It was in an effort to establish this sort of orientation that I came up with the outline I forwarded. I doubt too many business types will understand or even care about phrasing like "module mod_log_referrer" or "log file format". Most businesspeople just want to know that something works, not how and why it works. And they want to know in terns they understand what it can do for them. > For example, here is the place where to cover aspects as power
This might be outside our area of responsibility. Seems to me the members of the core group of developers would have to contribute to/agree to this.
There is even the need of documentation affording the internal
You must be psychic. This is another suggestion that several of the core group made to me when I originally aproached them re: helping out. >4. build a DocPortal as proposed by Kraaij, and evaluate the needs of writing
Once again, I agree. I'd suggest case studies of existing Apache implementations of a number of degrees of sophistication, as well as studies/popularizations of our efforts. >6. in which format/structure must we produce this bunch of data?
These aren't the only decisions of this kind. We'll also need to provide for a variety of means of delivery. >7. don't forget the target of it all! Query the Apache user base for which kind
>
Ambitious and stimulating indeed! I think the possibility of aiding and influencing the acceptance of something like Apache is exciting and worthwhile. Take care. Michele Received on Wed Nov 04 15:22:24 1998 This archive was generated by hypermail 2.1.8 : Thu Aug 24 2006 - 14:44:47 EDT |
||||||||||
|
|||||||||||