We track bugs and feature requests in gnome's bugzilla,
maybe you would like to see a list of all open
documentation bugs?
Interesting Links:
The following links are for further sites that can help with the
documentation and review process.
DocBook: The Definitive Guide.
DocBook XSL: The Complete Guide.
GNOME Human Interface
Guidelines
For both reviewers and documentation writers:
Please read the following guides. The new docs are based on the GNOME2 XML docbook system.
Everyone wishing to help please
follow these guides where possible when reviewing and/or writing docs.
The GNOME Documentation Style Guide
The GNOME Handbook of Writing Software Documentation
We suggest also subscribing to gnucash-devel.
Reviewers;
Please check out the documentation module from the GnuCash CVS -
gnucash-docs. For those not familiar with cvs, the GnuCash website has a
description. The only change
to get the docs is to change the checkout gnucash to checkout
gnucash-docs. You can also start from the current docs tarball.
The best way of retaining comments about docs in an easy to find
way for everyone would be to use bugzilla.gnome.org to file the bugs
under documentation. This can also be done using bug-buddy.
Writers;
Also checkout the docs cvs as above. The usual procedure for
contributors to GnuCash is to initially submit patches to the
gnucash-patches mailing list. We will handle getting the patches added into CVS until you are given an account. You can also add the patch to a bug report in bugzilla if you wish.
Please let other writers know which
section you wish to tackle. Please forward this to gnucash-devel so
that people can say 'hey I'm doing that already' or 'go ahead and do it'.
You may also want to retain a local copy of the old documentation to
refer to when writing. This still has a lot of useful information in it
which hasn't been transferred to the new docs