inFuse

h1. 02/15 Discussion on repositories

*Participants:* 

Ellon, Quentin

*Goal of the meeting:* Decide on a structure for the internal LAAS repository containing all code related to InFuse. The interest of the discussion is twofold: define the architecture, but also how we are going to use docker for deployment/integration

h2. Solution proposed

We discussed mainly three solutions for the repository:

1 *Monolithic structure, containing the entirety of the project:* this solution has the advantage of the "all-in-one", but we have to work on a solution to be able to compile only parts of the project

2. *Several "big" repos:* 1 for all the DFPCS, 1 for the Simu, 1 for the displays, 1 for the tools, 1 for the 3rd party libraries, etc... This has the advantage of the pick what you want, but multiplies the sources

3. *One repo = one thing:* 1 for EVERY DFPC, 1 for the Simu, 1 for every type of display, etc... This is too much