Re: [vchkpw] vpopmail documentation initiative

2003-08-14 Thread Tom Collins
On Wednesday, August 13, 2003, at 12:08 PM, Ron Guerin wrote: Wouldn't it be nice if we could get together and produce comprehensive vpopmail documentation? Wouldn't it be even nicer if we could distribute that documentation with vpopmail? We can! And I'd like to start the ball rolling by

Re: [vchkpw] vpopmail documentation initiative

2003-08-14 Thread Ron Guerin
On Wed, 2003-08-13 at 17:23, Ajai Khattri wrote: Also, do you have an FAQ of some kind? (I haven't looked). We ought to have some sort of cookbook will tried and proven solutions to common scenarios... Let's start one. I'll get into the DocManager after business hours today and see what

Re: [vchkpw] vpopmail documentation initiative

2003-08-14 Thread Ajai Khattri
Tom Collins wrote: I've enabled the DocManager feature of our SourceForge project, and Ron is the editor. If you have vpopmail-related documentation to contribute, please submit it here: http://sourceforge.net/docman/?group_id=85937 This is simply excellent! Also, do you have an FAQ of some

[vchkpw] vpopmail documentation initiative

2003-08-14 Thread Ron Guerin
Greetings all, I know some of you (like myself) have probably poked around in the vpopmail docs and maybe fixed a spelling error or added a new command line option to your local documentation. Others may have prepared HOWTO documents describing their setup, as I also was thinking of doing.

Re: [vchkpw] vpopmail documentation initiative

2003-08-14 Thread Evren Yurtesen
You have a point but you cant possibly make a documentation which describes every possible situation. You can give the basics and let the user use it as required. I think the most important thing which needs documentation is the ./configure switches of these programs. The rest is quite trivial,

Re: [vchkpw] vpopmail documentation initiative

2003-08-14 Thread Ron Guerin
On Wed, 2003-08-13 at 14:16, Evren Yurtesen wrote: You have a point but you cant possibly make a documentation which describes every possible situation. You can give the basics and let the user use it as required. I agree 100% complete documentation of all possible scenarios is impossible.