CONTRIB(1)                     mrtg                    CONTRIB(1)



NNNNAAAAMMMMEEEE
       contrib - Contribution Guidelines for MRTG

SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
       If you have written an extension to mrtg or created a bug
       fix, please consider contributing it to the project. As I
       get quite a number of contributions every week, here are a
       few guide lines which explain how to contribute so that I
       can use the contribution without too much additional work.

TTTTRRRRAAAANNNNSSSSLLLLAAAATTTTIIIIOOOONNNNSSSS
       MRTG messages have been translated to a number of lan-
       guages. But there are still many which have not been cov-
       ered yet. If you want to add yours, go into the
       _m_r_t_g_-_2_._9_._1_7_/_t_r_a_n_s_l_a_t_e directory, and follow the instruc-
       tions given in the _R_E_A_D_M_E file.

DDDDOOOOCCCCUUUUMMMMEEEENNNNTTTTAAAATTTTIIIIOOOONNNN
       All documentation of mrtg is done with the perl PPPPOOOODDDD sys-
       tem. If you want to learn about it, type

        perldoc perlpod

       and read the instructions. If you have bug fixes of addi-
       tions to the existing documents, make sure you modify the
       PPPPOOOODDDD files and not the HTML or txt versions.

PPPPAAAATTTTCCCCHHHHEEEESSSS
       When you have created your modification or extension to
       mrtg and want to submit it to me, please create a patch
       for the files which you have modified.  Do not send entire
       files unless they are new.

       To create a patch, get hold of a copy of GNU diff (Many
       Unix systems will have this installed already. In the NT
       world you might want to get http://sources.redhat.com/cyg-
       win/ to get all the nice GNU tools available.)  and type

        diff --unified --ignore-space-change file.orig file > simple.patch

       or if you have modified several files do

        diff --recursive --unified --ignore-space-change dir.orig/ dir/ >long.patch


DDDDOOOOCCCCUUUUMMMMEEEENNNNTTTTAAAATTTTIIIIOOOONNNN
       I take documentation very seriously. When ever you create
       a new feature for mrtg which you want to get included in
       the official release your patch must also contain modifi-
       cations for the relevant pod file in the _d_o_c tree or for
       the documentation sections of _c_f_g_m_a_k_e_r and _i_n_d_e_x_m_a_k_e_r.

AAAADDDDDDDDRRRREEEESSSSSSSS
       Send your patches, translations and contributions to
       Tobias Oetiker <oetiker@ee.ethz.ch>

AAAAUUUUTTTTHHHHOOOORRRR
       Tobias Oetiker <oetiker@ee.ethz.ch>



2001-06-05                    2.9.17                   CONTRIB(1)
