Submitting patches and features: Difference between revisions

From OpenPetra Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
The source code is managed with the Git source code versioning system, the official git of openPETRA is hosted at Sourceforge (http://git.openpetra.org).
The source code is managed with the Bazaar source code versioning system, the official repository of openPETRA can be browsed here: http://code.openpetra.org.


Please understand that we will provide write permissions only to the core members of the development team, just to keep the project on one track (refered to as 'developer access' below). We very much need your contributions though, and we will aim to quickly deal with submitted patches and code.
Please understand that we will provide write permissions only to the core members of the development team, just to keep the project on one track (refered to as 'developer access' below). We very much need your contributions though, and we will aim to quickly deal with submitted patches and code.


The easiest would be if you set up a free account on http://github.com and push your version there, and post in the [https://sourceforge.net/apps/phpbb/openpetraorg/viewforum.php?f=12 'Submit patches' sub forum] the link to your commit, eg. http://github.com/tpokorra/OpenPetraOrgTest/commit/621a1ccf2966afedb9923cb6efff1670966a997a. Then we can cherry-pick your commit and merge it into the official openPETRA git at Sourceforge.
We are currently working on an easy way how we can create developer branches on the main repository without giving write access to the main development trunk. Please remind us to UPDATE THIS TEXT!

Revision as of 16:23, 20 December 2010

The source code is managed with the Bazaar source code versioning system, the official repository of openPETRA can be browsed here: http://code.openpetra.org.

Please understand that we will provide write permissions only to the core members of the development team, just to keep the project on one track (refered to as 'developer access' below). We very much need your contributions though, and we will aim to quickly deal with submitted patches and code.

We are currently working on an easy way how we can create developer branches on the main repository without giving write access to the main development trunk. Please remind us to UPDATE THIS TEXT!