Why not merge ecoCode-common into ecoCode ?

[standousset]

While browsing through the two repos : (1) ecoCode and (2) ecoCode-common, I was wondering why we have those two repos.

The main repo ecoCode seems like a good place for :

• having the lists of rules (with the matrix of the state of each rule by language)
• AND having the documentation for starting contributions, code of conduct, explanation about tools...

What are the reasons for the separations ? Too many repos can create confusion.

cc. : @dedece35 / @glalloue

P.S. : I also use the opportunity to (re)test the Discussion feature in GitHub as decided recently on the Slack of the team. If necessary this disussion can be converted into an issue (for instance if we need to merge the two repos) and we can follow the tasks with GitHub issues kanban boards.