Propel Development Guidelines

We'd like to encourage everyone to contribute to the project in whatever ways they can. This is a volunteer project; all help is greatly appreciated.

We don't have a rigid styleguide or set of rules for contributing to Propel; however, with the goal of making things easier for all developers, here are a few suggestions:

• Get feedback from other people.
  This is what the Mailing Lists? and this Trac project management system are for. It is always a good idea to talk to other devs on the mailing lists before committing changes.
• Use Trac tickets.
  This is important to track progress and activity. If you start working on an issue, accept the ticket. After you have finished, close the ticket, and add information about the changeset in the comment fieldFootNote(This can be done using the ''changeset'' command, see TracLinks for more information)?.
• Write tests Please write tests for new functionality. See Development/Guidelines/WritingUnitTests for instructions.
• Stick to the Coding Standards
  (which are not really Coding Standards... go and see what they are about.)
• Use meaningful commit messages and reference tickets.
  See SVN and Tickets.

FootNote?