------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=136146         




------- Additional Comments From endres physos org  2006-10-29 02:04 -------
Ok

The good old wiki debate again. 

Funny how throwing the word "wiki" in anything writing related makes 
non-writers go "yes, lets just use a wiki and our documentation will magically 
just appear" and real writers cringe. 

First, writing documentation is very different from fixing a bug in a doc.

Second, who will maintain the wiki, since I can not see the manpower for 
weeding out the crap people produce suddenly appear. Throwing more people at a 
problem is what makes wikipedia more closed every day.

Third, Olaf and I are working on adding the [edit] function on docs.kde.org 
ASAP. This will send a diff to the docs maintainers and can be reviewed before 
inclusion.

I think thats what people want basically. A way to extend or correct 
documentation without even starting up their mail client. Since thats all that 
is needed right now.

It is nowhere said you have to learn DocBook to write documentation. You can 
simply write plain text and send it to the list.

Again, Olaf and I will add the new and improved [edit] function to docs.kde.org 
ASAP. 

I can not see in any way how a "dump" of a wiki can be easily integrated in our 
system, which allows translations into over 80 languages and thus has 25 
languages translating the docs. 

When all the people asking for a wiki would please calm down for a moment and 
then start to think how this magical wiki can be transformed into a format 
allowing for well formed PDFs, translation templates, HelpCenter compatible 
formats, HTML, PostScript, screen reader compatible formats, ... ?

DocBook is used for a reason. But it is not needed to write DocBook to 
contribute to KDE documentation already. If you are not able to use a text 
editor and a mail program, I wonder how you want to write technical 
documentation.

Reply via email to