Consider merging or separating eoxserver and core
Currently core is heavily intertwined with eoxserver, which leads to some overhead (vs-deployment#22 (moved) , #45 (moved) , vs-deployment#9 (moved) ). This is very visible e.g. when the configure.sh needs to be adapted or when releases need a tag in eoxserver and core.
From the point of view of VS, the structure would be simpler if eoxserver would be merged into core (or the other way around).
If this is not possible, maybe there's also a way to integrate eoxserver directly as a VS component and make core into an independent component which might talk to eoxserver via http.