Contributing bugfixes and enhancements to OGRE is always welcome. We only accept contributions in the form of patches, which are diffs against a your current version of OGRE. We prefer diffs against the latest Subversion copy if possible (stable branch for bugfixes, trunk for new features), although diffs against the last stable release are also acceptable. Details are shown below.

Contributor License Agreement

All contributors must agree to the OGRE contributor license agreement. Complete the details at the bottom of the agreement and scan/email or fax it to the address given at the bottom. The license agreement is required to ensure that OGRE can continue to be managed centrally and licensing enforced.

Coding Standards

Please make yourself familiar with our Coding Standards before submitting your patch. Whilst we will fix up valuable patches it would be appreciated if you tried to stick to our styles and conventions in the first instance.

Command-line patch creation

If you have the command-line ’svn’ tool available, you can create a patch from the root of the Ogre source tree like so:

svn diff > patch.txt

This will create a patch file called patch.txt for the existing files you have altered. If you created any new files, they will need to be included separately.

Creating a Patch using TortoiseSVN

Simply right-click on the ogre source folder, and select TortoiseSVN > Create Patch…, then pick a file to save the diff to. Again this only covers existing files in the ogre repository, if you created any new files, they will need to be included separately.

Submitting the Patch
Zip or tar the patch file and any new files you need to include, then use our Patch Tracking System to add a new patch record and upload the patch archive. Again, please make sure you have completed the OGRE Contributor License Agreement otherwise your patch may be rejected.