Split repository

[jycr]

As discussed on Slack, repositories should be split based on languages and/or platform.
This is so that each plugin can have its own development cycle.

For the "code" part, I found several methods:

• GitHub Docs - Splitting a subfolder out into a new repository
• How to split a git repository into two different ones
• Splitting Your Git Repo While Maintaining Commit History
• Git — How to Split Git SubDirectory into Separate Repository?
• Difference between git filter-branch subdirectory-filter & git subtree split -P

To migrate issues, I found this:

• GitHub Docs - Transferring an issue to another repository

[dedece35]

To complete this issue, only to do once all (or most) actives PRs merged (no to report opened PRs)

[dedece35]

Status :

• PHP OK : https://github.com/green-code-initiative/ecoCode-php
• Python OK : https://github.com/green-code-initiative/ecoCode-python
• Java OK : https://github.com/green-code-initiative/ecoCode-java
  • module "java-plugin" disabled but kept to keep current PRs "alive" (to simplify to comparison between PR sources and actual java-plugin sources) - to delete once all java PRs will be closed
  • a lot of files for development of java-plugin were deleted
  • module "java-plugin" deleted
  • all pom.xml cleaned

TODO :

• discussion to see if all file of ecocode-rules-specification module have to be moved to root or if we keep this module to create another one in the future for rules website (discussion with core-team)
• all remained PRs and issues dealing with java, php, pythin plugins will be reviewed and corrected in new repositories (issues and PRs won't be moved to new repositories for simplicity)