Re: Call for documentation

["Kurt D. Zeilenga" <Kurt@OpenLDAP.org>]

Anyone is welcome to contribute documentation (and/or source
code). Guidelines are the same as for source code.  See
<http://www.openldap.org/devel/> for contributing and other
guidelines.  Also, the developer's FAQ has specific information
regarding how to contribute to the Admin Guide.  Other
standalone documents are also welcomed.

Kurt

At 07:56 AM 2002-03-19, Raf Meeusen wrote:

>First of all, nothing should stop you from contributing documentation.  If 
>you write yourself the docs that you think are sufficient for installing, 
>configging and maintaining an openldap tree, than more people will be 
>helped.
>
>Secondly, you should post them on the openldap.org site.  Or you attach 
>them in some way to the Admin Guide, or you make another man page, which 
>can be read by interested parties.  I've no clue who's currently in charge 
>for the documentation, nor who's maintaining the www.openldap.org site, so 
>I hope Kurt, Howard or some other core member will reply to this mail for 
>further information.
>
>And 3th.  There's a lot of information to be found in the Archives, 
>bayour.com, search engines, etc.  So with a little bit of effort, you 
>should be able to figure out most of your problems.  The other ones, which 
>aren't so trivial, are mostly answered by members of this list.
>
>So, if you feel like helping the rest of us out with documentation, or 
>whatever other contributions, you're more than welcome!
>
>Regards,
>
>Raf
>
>
>On Tue, 19 Mar 2002, Ken Schneider wrote:
>
>> ivan wrote:
>> > 
>> > On 18 Mar 2002, Brandon Young wrote:
>> > 
>> > Agree.
>> > 
>> > I had the same problems and I an not a complete stranger to
>> > Unix/Linux.
>> > 
>> > There should be a collective effort to make documenting
>> > OpenLDAP for the end users. It is a great technology and it is needed by
>> > the open source community.
>> > 
>> > 
>> > 
>> 
>> I agree. The single MOST IMPORTANT item that will spur on an
>> applications use is documentation written in plain end user terms with
>> plenty of working examples. No should, could examples.
>> 
>>