Refactor repository
The repository needs to be refactored.
New proposed hierarchy
-
Top level hierarchy into core code, main config, main doc, demo, PoC -
Core sub hierarchy organized per components: CME, CMS, ... and a common (shared) folder. -
Component folders have code
,test
,docs
,config
. -
Sub-hierarchy of PoC folder organized per independent application. -
Repo subdirs should be split into shared code (common) and per-component events. -
Move documentation from gitlab.datascience.ch
into doc folder (issue #32 (closed))
Organize branches into development
and master
(dynamico_dev
should be for dynamico specific code only).
This is to be revised and adapted as we progress on the CI/CD front.
Intention is to break down the repository into independent repositories in the future to further decouple the components from the applications (PoC) from the target deployment environments.
Fotis proposes: fork to more repositories once components reach a maturity level (v1.0 or some defined milestone). It is great, for ci/cd purposes, to have the web-facing documentation on a separate repository.
Edited by erbou