Contribute

Development

There are several methods for submitting patches. You can send the patch to the Bcfg2 mailing list, create a trac ticket with the patch included, or submit a pull request on github. In order to submit a ticket via the trac system, you will need to create a session by clicking on the Preferences link and filling out/saving changes to the form. In order to be considered for mainline inclusion, patches need to be BSD licensed.

The web interface to the git repository, github or the source browser can give you an overview of the source code. For more details about the usage of the git repository, please refer to the Submitting Patches page.

Several resources for developers exist at http://docs.bcfg2.org/development/.

Bcfg2 is the result of a lot of work by many different people. They are listed on the contributors page.

Testing Prereleases

Before each release, several prereleases will be tagged. It is helpful to have users test these releases (when feasible) because it is hard to replicate the full range of potential reconfiguration situations; between different operating systems, system management tools, and configuration specification variation, there can be large differences between sites.

Adding to the Common Repository

The Bcfg2 common repository is a set of portable examples that new repositories can be based on. This repo has several parts. The first is a series of group definitions that describe a wide range of client systems. The second is a set of portable bundles that have been ported to use these groups. This makes these bundles transparently portable across new client architectures.

This approach has several benefits to users

• Configuration specification can be shared across sites where appropriate
• This common configuration specification can be reused, allowing sites to migrate to new systems that other sites have already ported the common repository to
• Setup of new systems becomes a lot easier.