Changes between Version 24 and Version 25 of Contribute
- Timestamp:
- 11/05/10 04:08:05 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Contribute
v24 v25 5 5 There are several ways users can contribute to the Bcfg2 project. 6 6 * Developing code 7 * Testing pre releases7 * Testing pre-releases 8 8 * Adding to the common repository 9 9 * Improving the wiki … … 13 13 == Development == 14 14 15 Send patches to the [wiki:MailingList bcfg mailing list] or create a trac [https://trac.mcs.anl.gov/projects/bcfg2/newticket ticket] 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 [https://trac.mcs.anl.gov/projects/bcfg2/prefs 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 most convenient way to prepare patches is by using `git diff` inside of a source tree checked out of subversion. The source tree can be checked out by running:15 Send patches to the [wiki:MailingList bcfg mailing list] or create a trac [https://trac.mcs.anl.gov/projects/bcfg2/newticket ticket] 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 [https://trac.mcs.anl.gov/projects/bcfg2/prefs 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 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: 16 16 17 17 {{{ 18 18 git clone git://git.mcs.anl.gov/bcfg2.git 19 19 }}} 20 21 The [http://git.mcs.anl.gov/bcfg2.git/ web interface] to the git repository or the [source:trunk/bcfg2 source browser] can give you an overview of the source code. 20 22 21 23 Several resources for developers exist in the wiki: