Hi Daniel, > Just dropping a quick note to say that I'd be happy to write documentation > for a KDE program. Most of the programs that I use regularly already have > decent documentation, so a list of programs that need documentation > improving (or writing) would allow me to choose a program that I could cope > with working on.
I notice that Brad has already mentioned a few places to get involved - if any of those appeal to you, drop us a note, and we'll help you get together what you need to get started (which isn't much, but might vary depending on what you're working on). If you can't find anything that interests you in that list, there are still plenty of other ways to get involved. Just ask, and we can suggest some other things. One thing that's important to mention is that you don't have to learn DocBook (which is the format we use for documentation). It's quite a steep learning curve, and sometimes new contributors have trouble with it, but the good news is that you don't have to worry about it - you can write in plain text and we'll do the rest. If you have any other questions, or have trouble finding something to work on, don't hesitate to contact us, either here on the list, or if you're on IRC, on #kde-docs on irc.freenode.net (where I'm PhilRod, and you can find several other members of the docs team). Regards, Philip -- KDE Documentation Team: http://i18n.kde.org/doc KDE Documentation Online: http://docs.kde.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://mail.kde.org/pipermail/kde-doc-english/attachments/20060219/220c6dda/attachment.sig
