Is a fact that the current codebase does contain a mix of various styles.

There is no style formatting suggested in the contributing guidelines and there is no automation in this direction.

I do believe that having a consistent style across the codebase can increase the readability and improve the collaboration.

There are a few low-hanging fruits that can be easily implemented in this direction:

• mention the adopted code-style in the Contributing document
• integrate an automatic code formatter

I don't have any strong preference on the code style to be adopted, as long as it's one 🙂 .

A possible path-forward, after having identified a style, is to apply it to the project, this can be a pretty difficult operation since it will invalidate and need a rebase of all the open PRs.
Hence I suggest a gradual migration:

• integrate the automatic formatter at the top of the project disabling it by default
• selectively enable the automatic formatting in sub-modules when the main stake-holders are ok with it
• check the style in CI to avoid regressions
• eventually apply it to the entire codebase