Maintaining coding style is hard without good tool support. EditorConfig seems to be the best way to accomplish that over a wide variety of platforms. Are there any volunteers to try to implement ITK’s style guide in an
.editorconfig file? It is totally OK if this is done incrementally - somebody does a first pass implementing a few rules, which gets expaned by someone else etc.
A possible starting point would be translating ITK’s uncrustify configuration files. uncrustify_itk.cfg is meant to not overly modify the user-written code, even if it means not fully enforcing the ITK style. uncrustify_itk_aggressive.cfg tries to enforce as many rules as possible, with a side-effect of creating more un-compilable modifications.
Also, as we are doing a major overhaul of the library right now, it might be worthwhile considering a change in code style. We could relax the rules somewhat, or turn some rules into recommendations (e.g. space around template parameters
FilterType< ImageType >). We could also completely rework the rules to make them easier to be automatically and reliably enforced (by e.g. clang-format). A more standard style (such as Allman) would be easier to enforce than a completely custom style (currently effective ITK style).