1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
\r
4 <link href="style.css" REL="stylesheet" TYPE="text/css" MEDIA="screen">
\r
5 <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
\r
6 <title>Kiriwrite Documentation - User Documentation - Chapter 6: Contributing to Kiriwrite</title>
\r
9 <div class="menubarback">
\r
10 <div class="menubar">
\r
11 <span class="apptitle">Kiriwrite</span>
\r
12 <a href="index.html">Index</a> | <a href="user.html">User
\r
13 Documentation</a> | <a href="tutorial.html">Tutorial Documentation</a> |
\r
14 <a href="developer.html">Developer Documentation</a>
\r
17 <div class="pageinformation">
\r
18 <span class="pagetitle">Chapter 6: Contributing to Kiriwrite</span><br><br>
\r
20 <span class="heading">6.1: Contributing</span><br><br>
\r
22 You can contribute to Kiriwrite in many different ways like the following examples:
\r
24 <li>Translate Kiriwrite (program or documentation) so that it can be used your own local language.</li>
\r
25 <li>Add functionality to Kiriwrite.</li>
\r
26 <li>Write a presentation or database module.</li>
\r
27 <li>Report a bug or fault (either with Kiriwrite itself or the documentation).</li>
\r
29 When reporting a bug, you should give the version number of Kiriwrite, what operating system you are using, what web server you are using and the version of it, the version of Perl you are using (and if possible the version of the Perl module that is causing the bug), what the error message of the bug is and how to recreate the bug (if possible).
\r
33 For more information on how to contribute to Kiriwrite visit http://xestia.co.uk/kiriwrite or visit the BerliOS project site at http://developer.berlios.de/projects/kiriwrite . A list of stuff that needs doing can be found in the TODO file in the Kiriwrite package (remember to check the latest Kiriwrite package's TODO file for the latest on what needs doing).
\r