I did read it, although his quoting style is terrible to read. My idea
is to first document everything in the wiki and then build the manpages
out of that information available in the wiki. So that putting the man
pages together is just some markup and reordering work, but no real
writing of documentation is required.
hehehehe, Philipp, when I read what you said here I thought to myself:
"Damn, if he thinks exactly what I think, how can we disagree?"
What I'm trying to do on the wiki site is exaclty what you said: "So that
putting the man pages together is just some markup and reordering work, but
no real writing of documentation is required"
This is exactly my plan.
But I thought it would be easier to start the documentation on the wiki
site already in a manpage style, so that putting man pages together is just
some markup work, but no real writing of documentation is required (see,
using your words but cutting off the reordering phase since it would
already be done)
But I realize I'm thinking different from everybody, so I'll stop doing
those manpages on the wiki website right now.
The work I did in qmail-control(5) is still useful and will help us in
saying which file is read by which programs, what's a valuable information
that the current documentation lacks.
Do you have an idea for what's the next step now?
Bruno.
