Code standardization, document and responsible role?

Question

Project management

Suppose a team has gathered at the beginning of some large project and they make decisions on the architecture, and in particular on the unification and standardization of writing code. For example, CamelKeys or BEM. Where is put { , 8 or 4
Well, such a trifle, for example.
Who should ideally be responsible for such details (do I think that QC is correct?), And what will such a document be called, where all this will be written out?

ZYZH I remember reading such a document, but I forgot where and what office, where such details were written out, and there it was told in the article who and how it was taken. Do you know what article I'm talking about?

Answer 1

Different languages ​​have their own standards. Just google something like {language} style guides. For example, for php it will be PSR , for js, for example, a guide from airbnb or ideomatic.js .
When you use generally accepted coding standards, everything is easier. Linters already have these style guides a priori. Inside the team, you simply agree on which ones you will follow. If you want to use something of your own, share custom configs for team members.
What is the name of such a document? Probably the Code Style Guide. Perhaps you are talking about the article https://www.pullrequest.com/blog/create-a-programm...
There are also synonyms: coding guidelines, coding standards, or coding conventions.
Who controls? Well, if there are several levels of code verification:

• developer level - using a linter in the code development environment
  
• team lead/senior developer level - during code review
  
• the level of handlers in the version control system - when performing push or merge (did not pass - we get a refusal)
  

Answer 2

camelcase, 8 or 4

it's like a style, not architecture. Such decisions are usually made by the community, represented by the core team of developers of the language and standard libraries ... And then it is flashed in linters.