CONTRIB(1)                     mrtg                    CONTRIB(1)



NNAAMMEE
       contrib - Contribution Guidelines for MRTG

DDEESSCCRRIIPPTTIIOONN
       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 guidelines which explain how to contribute so that I
       can use the contribution without too much additional work.

TTRRAANNSSLLAATTIIOONNSS
       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_._2_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.

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

        perldoc perlpod

       and read the instructions. If you have bugfixes or addi-
       tions to the existing documents, make sure you modify the
       PPOODD files and not the html or txt versions.

PPAATTCCHHEESS
       When you have created your modification or extension to
       mrtg and want to submit it to me, please crate 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 old-file new-file > simple.patch

       or if you have modified several files do

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

DDOOCCUUMMEENNTTAATTIIOONN
       I take documentation very seriously. Whenever you create a
       new feature for mrtg which you want to get included in the
       official release, your patch must also contain modifica-
       tions for the relevant ppoodd 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.

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

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



2.9.27                      2003-02-19                 CONTRIB(1)
