idea from @jycr :

SonarQuabe has a centralized repository to describe each of its rules, which is independent of the different existing implementations:
https://github.com/SonarSource/rspec

This makes it possible to have a centralized vision of the rules, and their variations according to the programming languages.
This also helps to avoid problems/conflicts in assigning identifiers (keys) for the rules.

This also makes it easier to write descriptions (in asciidoc/markdown).

Perhaps this orientation could become interesting for the future of ecoCode rules?

According to me, we should have a special meeting for this point to initiate this refactoring to :

• describe context
• describe your first idea, @jycr
• make a discussion with core team
• create an action plan, here