Open Documentation Tasks

As a volunteer project, it's hard for anyone to say "Do this" or "Do
that". We can make a few suggestions, so on this page will be listed
documents that the team knows for sure are in urgent need of help.

Please bear in mind, that although we won't be telling you specifically
what to work on (unless you really can't decide!), it's very important that
you coordinate with the team. There are limited writer resources to go
around, and doubling up on work may mean we can't use your work. Better to
coordinate our resources so that if two of you wish to work on the same doc,
you can work as a team, and get results that are twice as nice.

In practise, coordination is as simple as dropping a note to the
kde-doc-english mailing list to say that you are working on a particular job,
and routing your work back through us when you're ready to submit, for
markup and proofreading. You don't need to be subscribed to write to this
list, although it's a good idea to subscribe anyway, as the list is low
traffic.

KOffice needs you!

KOffice is in need of help.

For KOffice documents, you can use the released version (KOffice 1.5/1.6), which
will serve as the basis for the upcoming release, KOffice 2.0.
Small tasks will be filed in the bugs database or posted on the
KOffice Documentation
Jobs page.

However, a lot of the KOffice documentation is pretty sorely out of date, so if
you'd like to take on updating larger portions, say an entire section or
chapter, we'd love to have you helping out. Information about this is posted on the jobs page as well.

Open jobs in the bugs database

The bugs database is a good place to store the open jobs we have. If you
want to take on one of these, there should be instructions in the bug itself.
As usual, let us know what you're working on, and also feel free to comment
directly on the bug/TODO item, or add patches directly there.

If you have an idea for another document, or you found something on your
own that you'd like to work on, that's great too. Or if you've looked at all
the jobs above, and haven't found anything that strikes your interest, write
to the team on the mailing list, and we will try to come up with
something.