Final Integration Tracking in GitHub Consolidation

[agrignard]

We know for many different reasons that it's difficult to have all the code in the same repo. However with the deadline arriving I think it's getting critical to consolidate the github not only on the code but on the documentation also). Right now it's getting very hard (not to say impossible) to track the evolution of the project.

This is the current activity that one can see of the github now appart ABMobility nothing has been updated since more that 2 weeks (which is not true but this is what we see) so it makes impossible to know who is working on what

The best solution would be to have everyone trying to push in this repo at least to update the submodules (when they exists) so we know something has changed.

@yasushisakai what do you think? What about forcing the update of the submodules?

[yasushisakai]

@agrignard should we delete irrelevant submodules? (e.g. graphic studies)

People (@popabczhang @RELNO) can ping me or @aberke if they need help updating the submodule.

[agrignard]

If they are not really used yes I think we can delete them

[yasushisakai]

related #67 Should we have a convention for this project where to have documentation? wiki? README?

[agrignard]

I think The wiki is the place with a bit of reorganization. especially if we want to put picture we don't want to put image in the repo so the README should be for minimal information. Like the root README could have some basics information about the project and then point to the wiki for more specific details.

[yasushisakai]

This issue will kept alive, until the deployment && documentation on wiki is complete.

[agrignard]

merge in #75