chris@39: = Contributing to Redmine with git and github
chris@39: 
chris@39: (This is a beta document. If you can improve it, fork it and send a patch/pull request.)
chris@39: 
chris@39: The official repository is at http://github.com/edavis10/redmine
chris@39: 
chris@39: Official branches:
chris@39: 
chris@39: * master - is automatically mirrored to svn trunk. DO NOT COMMIT OR MERGE INTO THIS BRANCH
chris@39: * [0.6, 0.7, 0.8, 0.9, 1.0,...]-stable - is automatically mirrored to svn release branches. DO NOT COMMIT OR MERGE INTO THIS BRANCH
chris@39: * integration-to-svn-trunk - this branch is a git-only branch that will track master (trunk). Any code in here will be eventually merged into master but it may be rebased as any time (git-svn needs to rebase to commit to svn)
chris@39: * integration-to-svn-stable-1.0 - this branch is a git-only branch that will track the 1.0-stable branch in svn.  Any code in here will be eventually merged into master and 1.0-stable but it may be rebased as any time (git-svn needs to rebase to commit to svn)
chris@39: 
chris@39: I (edavis10) might have some other branches on the repository for work in progress.
chris@39: 
chris@39: == Branch naming standards
chris@39: 
chris@39: Redmine has two kinds of development:
chris@39: 
chris@39: * bug fixes
chris@39: * new feature development
chris@39: 
chris@39: Both bug fixes and new feature development should be done in a branch named after the issue number on Redmine.org.  So if you are fixing Issue #6244 your branch should be named:
chris@39: 
chris@39: * 6244
chris@39: * 6244-sort-people-by-display-name (optional description)
chris@39: * issue/6244 (optional "issue" prefix)
chris@39: * issue/6244-sort-people-by-display-name (optional prefix and description)
chris@39: 
chris@39: That way when the branch is merged into the Redmine core, the correct issue can be updated.
chris@39: 
chris@39: Longer term feature development might require multiple branches.  Just your best judgment and try to keep the issue id in the name.
chris@39: 
chris@39: If you don't have an issue for your patch, create an issue on redmine.org and say it's a placeholder issue for your work. Better yet, add a brief overview of what you are working on to the issue and you might get some help with it.
chris@39: 
chris@39: == Coding Standards
chris@39: 
chris@39: Follow the coding standards on the Redmine wiki: http://www.redmine.org/wiki/redmine/Coding_Standards#Commits.  Make sure you commit logs conform to the standards, otherwise someone else will have to rewrite them for you and you might lose attribution during the conversion to svn.
chris@39: 
chris@39: