**>Message-ID: <[EMAIL PROTECTED]>
**>Date: Mon, 2 Apr 2007 02:34:54 +0300
**>From: "Enver ALTIN" <[EMAIL PROTECTED]>
**>To: "XSG Telecom M.I. de Jong" <[EMAIL PROTECTED]>
**>Subject: Re: Queued DLRs
**>In-Reply-To: <[EMAIL PROTECTED]>
**>MIME-Version: 1.0
**>References: <AcdhezITmXnMn8SVR4GNrY3iDIOfBg==>
**> <[EMAIL PROTECTED]>
**>Cc: users@kannel.org
**>
**>
**>Try flushing the DLR queue. As always, details in User's Guide.
**>
**>http://www.kannel.org/download/1.4.1/userguide-1.4.1/userguide.html#AEN834
**>
**>Totally off-topic though, after reading many books on Agile Software
**>Development processes, including those from Ken Schwaber and Alistair
**>Cockburn, I think I understand why conventional development processes
**>tend to regard documentation as a required donkeywork. Now, agile
**>processes value working software over complete documentation but in
**>the case of Kannel we have both working software and excellent
**>documentation yet people actually don't read it. Now it feels like
**>there's something wrong here. Is this because documentation is so big
**>and full of so much information, or is it so badly organized that
**>people are having hard times reading it, or the product is so good
**>people think they can figure out themselves without the need of
**>reading the documentation, or people are being just lazy? Anyone? Hmm.
I think the problem is:
- complexity of Kannel's capabilities
- lack of background in the WAP/SMS/MMS implementation of new Kannel users
- overwhelming amount of technical information inside the Kannel
documentation
- not enough detailed/annotated examples
- incomplete glossary/bibliography
- lack of index
I tried to re-write the manual when I was writing a UUID module for
Kannel v1.3.1 (which my employer will not allow me to open-source), but
ran out of time resources. The major problem is that the document
is in DSSL (Docbook) format and there are limited editors (circa 2003)
that natively support it in a WYSIWYG mode. Additionally, it did not
use a version of DSSSL that can be XML validated. As a result, it's
a pain to re-write.
I ended up using VI, converting the whole document to dockbookx
(to support XML validation of the document), added section
numbering to keep myself from getting lost, hand edititing
the resulting document, and passing it through openJade to render
an HTML version for ever change. VERY time consuming.
I've been trying to find time to continue this but real-life
intrudes in my open-source ventures.
For anyone interested, here's what my old version looked like:
http://202.181.245.115/kannel-doc/1.3.1/userguide.html
See ya...
d.c.
