I thought the point of moving (AOLserver documentation) to a wiki was so that 
we could edit the manpages, which can then be turned into html pages, 
essentially to divide up the work, and make it easy for more people to help.

Nobody ever did much to actually do the editing, or moving the edits back into 
AOLserver CVS, so it is essentially a failed experiment. 

Moving the documentation part into another wiki will probably have the same 
outcome, and it places a large burdon and responsibility on one or two 
community members. 

What I have noticed is that the manpages are difficult (tedious) to write, and 
the html looks somewhat weird, but it at least matches up with Tcl and the 
existing AOLserver docs. 

Here is an example manpage:

http://junom.com/document/tWSDL/mann/wsnamespace.n

and the associated html page (generated from a makefile):

http://junom.com/document/tWSDL/wsnamespace.n.htm

Considering how little time is ever devoted to actually writing documentation, 
it seems like it would be more beneficial to use less technology, and rely on 
existing tools to reformat as needed. 

I have various sets of old documentation, which serve most of my needs, but 
are obviously very out of date. But they also contain the organizational 
structure of good documentation, which we inherited from the 2.* versions and 
essentially abandoned in 4.0 or earlier. 

tom jackson




On Thursday 20 March 2008 13:50, Dossy Shiobara wrote:
> On 2008.03.20, Rick Cobb <[EMAIL PROTECTED]> wrote:
> > Is the panoptic one still the one to edit?
>
> Yes--the dev.aolserver.com one is still read-only and won't accept
> edits now, anyway.
>
> A question was raised to me about moving it all into an OpenACS XoWiki.
> What does everyone think?  I'd be happy to hand over the
> content--and responsibility--if someone from the community is
> volunteering to do the work involved.
>
> -- Dossy


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> 
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Reply via email to