summaryrefslogtreecommitdiffstats
path: root/doc/development/index.txt
blob: 352000dc8919e5dbc6d2db5913fe21ed59b58605 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
.. -*- mode: rst -*-

.. _development-index:

=================
Bcfg2 Development
=================

There are many ways to get involved in Bcfg2 development. Here we will
outline some things that can help you get familiar with the various
areas of the Bcfg2 code.


Send patches to the :ref:`help-mailinglist` or create a trac
`ticket <https://trac.mcs.anl.gov/projects/bcfg2/newticket>`_
with the patch included. In order to submit a ticket via the
trac system, you will need to create a session by clicking on the
`Preferences <https://trac.mcs.anl.gov/projects/bcfg2/prefs>`_ link and
filling out/saving changes to the form. In order to be considered for
mainline inclusion, patches need to be BSD licensed. The most convenient
way to prepare patches is by using ``git diff`` inside of a source tree
checked out of git.

The source tree can be checked out by running::

    git clone git://git.mcs.anl.gov/bcfg2.git

Users wishing to contribute on a regular basis can apply for direct
git access. Mail the :ref:`help-mailinglist` for details.


.. toctree::
   :maxdepth: 1

   tips
   setup
   client-driver
   plugins
   testing
   documentation
   docstyleguide