Commit 75a70df3 authored by Martyn Welch's avatar Martyn Welch

Shift coding conventions to

The coding conventions form an important part of the contribution process.
Shift these to as part of the contribution process
documentation and to improve the versioning and change control.

Fix up links to this page that exist in current documentation.
Signed-off-by: default avatarMartyn Welch <>
parent 9fdeb94c
This diff is collapsed.
......@@ -65,7 +65,7 @@ cluttering this one.)
Before submitting any patch, please make sure that it passes this checklist, to
avoid the review getting hung up on avoidable issues:
1. All new code follows the
[coding guidelines](,
[coding guidelines](,
especially the
[API design guidelines](,
[namespacing guidelines](,
......@@ -102,9 +102,9 @@ guidelines](
one for variable mode, one for linked rollers, one for each animation mode,
1. All new code must be formatted as per the
[coding guidelines](,
[coding guidelines](,
not GNU `indent`.
1. There must be an example program for each new class, which can be used to
manually test all of the class’s main modes of operation (for example, if
......@@ -162,7 +162,7 @@ You must not amend copyright notices which are inserted by other people without
their explicit permission which must be recorded appropriately.
Apart from the license header, you should also include the
[vim modeline at the top of the file](
[vim modeline at the top of the file](
to help enforce consistent coding style.
Markdown is supported
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment