Difference between revisions of "Coding guidelines"

From Multi Theft Auto: Wiki
Jump to: navigation, search
m (Committing code)
Line 30: Line 30:
  
 
== What to code ==
 
== What to code ==
Generally, developers should try to stick to the [http://bugs.mtasa.com/roadmap_page.php Roadmap] when coding.  This lists the issues required to be resolved for the next release.
+
Generally, developers should try to stick to the [http://bugs.mtasa.com/roadmap_page.php Roadmap] when coding.  This lists the issues required to be resolved for the next release. Of course, if you're interested in something else, feel free to experiment and submit it.
 +
 
 +
== Style ==
 +
* We use 4 spaces instead of tabs.
 +
* Generally follow the style of the code that already exists.

Revision as of 01:42, 9 November 2010

Introduction

So you've decided to become a contributor to our project. Excellent! But before we can start accepting your code, there are a couple of things you should know about how we work. These are mostly guidelines and rules as to how your code should be structured and how it can be committed without upsetting any fellow contributors.

Code repository

Structure

Our code repository (SVN) is structured into number of different directories, which serve different purposes:

  • trunk: the current development trunk (latest but experimental)
  • branches: branches with groundbreaking research, radical ideas and other work-in-progress that is meant to be merged into the trunk at a later point, but also contains project milestones (which are kept away from the trunk for stability reasons)
  • vendor: unmodified third-party code and libraries (optionally linked to the appropriate third-party SVN repository through svn:externals)

Gaining and Losing Commit access

Commit access is granted after patches have been submitted, and the coder has proven to be competent. The subject matter of the patches does not matter, we are more interested in whether if you are granted commit access, you will be capable of mantaining a high standard of code and remaining cohesive with other project contributors.

Patches can be submitted in our Mantis Source Patches section. Usually commit access is gained after 2-3 patches, but this is not fixed and depends on the extent of the contributions.

After gaining commit access, if the contributor's commits are of a consistently low standard, or the user fails to stick to the rules, their commit access will be stripped and will be required to submit patches again.

Committing code

Keep in mind that your commits should initially be fixing or implementing existing issues on our Bug tracker. The Roadmap is especially important since it allows contributors to track down priority issues.

Please follow these guidelines for all your contributions:

  • Commits should be thoroughly tested when using the trunk. Commits that 'need to be fixed later' which directly affect the state of the mod will be reverted other than in exceptional circumstances.
  • If writing unstable or experimental code, a branch should be opened for each feature. Branches should not be "personal" to each user. This means that a branch should be created for a new feature, not for a user specific playground.
  • Log messages should always give a clear indication of the content of the change, without having to look at the code at all. Where appropriate, include the Mantis Issue number in your log message and keep your log messages consistent, e.g. Fixed #1234: description and notes here. When using branches, the name of the branch should be quoted in the message log, e.g. [customanimations] Added IFP support.

Ratings and comments

Ratings and comments are open for the public to review code and provide feedback. Please be mature and civilised when posting comments. Developers should try to review other contributor's commits and provide feedback as much as possible.

What to code

Generally, developers should try to stick to the Roadmap when coding. This lists the issues required to be resolved for the next release. Of course, if you're interested in something else, feel free to experiment and submit it.

Style

  • We use 4 spaces instead of tabs.
  • Generally follow the style of the code that already exists.