add doc on clang-format process

Author: KrisThielemans

CONTRIBUTING.md

@@ -29,23 +29,25 @@ This is our recommended process. If it sounds too daunting, ask for help.
 3. Create a branch in your fork with a descriptive name and put your fixes there. If your fix is
 simple you could do it on github by editing a file, otherwise clone your project (or add a remote
 to your current git clone) and work as usual.
-4. If your change is important, add it to the release notesfor the upcoming version, [see](https://github.com/UCL/STIR/blob/master/documentation/)
+4. Configure your editor and potentially even [pre-commit](https://pre-commit.com/), see
+[documentation/devel/README.md](documentation/devel/README.md).
+5. If your change is important, add it to the release notes for the upcoming version in the [documentation folder](https://github.com/UCL/STIR/tree/master/documentation/)
 and even the [User's Guide](https://github.com/UCL/STIR/blob/master/documentation/STIR-UsersGuide.tex) or other documentation files.
-5. Use [well-formed commit messages](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
+6. Use [well-formed commit messages](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
 for each change (in particular with a single "subject" line
-followed by an empty line and then more details). If the change affects comments only, it is recommended to put `[ci skip]` in your subject line. This avoids unnecessary computation, and clogging our Travis/Appveyor queues.
-6. Push the commits to your fork and submit a [pull request (PR)](https://help.github.com/articles/creating-a-pull-request)
-(enable changes by project admins.) Give your pull request a descriptive name (i.e. don't call if *Fix #issuenumber*. Be prepared to add further commits to your branch after discussion.
-In the description of the PR, add a statement about which Issue this applies to
-using [a phrase such that github auto-closes the issue when merged to master](https://help.github.com/articles/closing-issues-using-keywords/).
-7. Be prepared to add further commits to your branch after discussion.
+followed by an empty line and then more details).
 Please by mindful about the resources used by our Continuous Integration (CI) workflows:
   - Group your commits and only push once your code compiles and tests succeed on your machine (ideally you have sensible commit messages at every stage)
   - Use specific keywords in the first line of the last commit that you push to prevent CI being run:
      - `[ci skip]` skips all CI runs (e.g. when you only change documentation, or when your update isn't ready yet)
      - `[actions skip]` does not run GitHub Actions, see [here](https://github.blog/changelog/2021-02-08-github-actions-skip-pull-request-and-push-workflows-with-skip-ci/). Note: this can be in the main commit message.
      - `[skip appveyor]` does not run Appveyor, see [here](https://www.appveyor.com/docs/how-to/filtering-commits/#skip-directive-in-commit-message)
-8. After acceptance of your PR, go home with a nice warm feeling.
+7. Push the commits to your fork and submit a [pull request (PR)](https://help.github.com/articles/creating-a-pull-request)
+(enable changes by project admins.) Give your pull request a descriptive name (i.e. don't call if *Fix #issuenumber*. Be prepared to add further commits to your branch after discussion.
+In the description of the PR, add a statement about which Issue this applies to
+using [a phrase such that github auto-closes the issue when merged to master](https://help.github.com/articles/closing-issues-using-keywords/).
+8. Be prepared to add further commits to your branch after discussion.
+9. After acceptance of your PR, go home with a nice warm feeling.
 
 Suggested reading: 
 https://help.github.com/articles/fork-a-repo/, https://git-scm.com/book/en/v2/GitHub-Contributing-to-a-Project or https://guides.github.com/activities/forking/.

documentation/STIR-developers-overview.tex

@@ -1331,7 +1331,10 @@ \section{
 
 \section{Contributing to STIR}
 See
-\R2Lurl{https://github.com/UCL/STIR/blob/master/CONTRIBUTING.md}{STIR/CONTRIBUTING.md}.
+\R2Lurl{https://github.com/UCL/STIR/blob/master/CONTRIBUTING.md}{STIR/CONTRIBUTING.md}
+and
+\R2Lurl{https://github.com/UCL/STIR/blob/master/documentation/devel/README.md}{documentation/devel/README.md}
+for more information on editor settings etc.
 
 \subsection{Continuous integration testing}
 We use GitHub Actions and Appveyor for testing of every pull-request that was submitted on GitHub. PRs

documentation/release_6.0.htm

@@ -9,7 +9,7 @@ <h1>Summary of changes in STIR release 6.0</h1>
 
     <p>This version is 99% backwards compatible with STIR 5.x for the user (see below).
       Developers might need to make code changes as 
-      detailed below. Note though that the location of installed files have changed.
+      detailed below. Note though that the <strong>locations of installed files have changed</strong>.
       Developers of other software that uses STIR via CMake will need to adapt (see below).
     </p>
     <h2>Overall summary</h2>
@@ -285,6 +285,18 @@ <h2>New deprecations for future versions</h2>
     <H2>What's new for developers (aside from what should be obvious
       from the above):</H2>
 
+    <h3>White-space and style enforcement</h3>
+    <ul>
+      <li>We now use <tt>clang-format</tt> to enforce C++-style, including white-space settings, line-breaks
+        etc. This uses the <tt>.clang-format</tt> file in the root directory of STIR. Developers should
+        configure their editor encordingly, and ideally use <tt>pre-commit</tt>. It also has
+        consequences for existing branches as you might experience more conflicts than usual
+        during a merge. More detail is in
+        <a href="https://github.com/UCL/STIR/blob/master/documentation/devel/README.md">documentation/devel/README.md</a>.<br>
+        <a href="https://github.com/UCL/STIR/pull/1368">PR #1368</a>.
+      </li>
+    </ul>
+
     <h3>Backward incompatibities</h3>
     <ul>
       <li>