0215 » History » Version 4
Quentin Labourey, 2018-02-15 17:27
| 1 | 1 | Quentin Labourey | h1. 02/15 Discussion on repositories |
|---|---|---|---|
| 2 | |||
| 3 | *Participants:* |
||
| 4 | Ellon, Quentin |
||
| 5 | |||
| 6 | *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 |
||
| 7 | |||
| 8 | h2. Solution proposed |
||
| 9 | |||
| 10 | We discussed mainly three solutions for the repository: |
||
| 11 | |||
| 12 | 3 | Quentin Labourey | * *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 |
| 13 | 1 | Quentin Labourey | |
| 14 | 3 | Quentin Labourey | * *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 |
| 15 | |||
| 16 | * *One repo = one thing:* 1 for EVERY DFPC, 1 for the Simu, 1 for every type of display, etc... This is too much |
||
| 17 | 4 | Quentin Labourey | |
| 18 | After a long debate, we propose to use option 1, one big monolothic repo containing everything with the structure below: |