Contributing¶

Since we're still working on the coding style-guide (see #81) use the following list to check your merge-requests. As a general rule, stick to the conventions of the files you're editing.

• New features should come with a test. We'll require tests as soon as the testability of the code improves.
• The test-suite must pass (issue make test in your build directory)
• Don't use tabs
• Two space indentation, strip whitespace at eol
• Use meaningful commit messages
  • Keep the first line under 50 characters