forked from DevFW-CICD/edp-doc
doc(poc-structure): WiP some thoughts on the composition or physical structure of the product
This commit is contained in:
parent
2cb8e342a3
commit
c91444c98c
1 changed files with 11 additions and 1 deletions
12
README.md
12
README.md
|
@ -33,4 +33,14 @@ This is the Storybook of the PoC content structure (content is depicted top righ
|
|||
|
||||
This is the illustration of the [use cases (aka 'functionality') in the PoC content](https://confluence.telekom-mms.com/display/IPCEICIS/Proof+of+Concept+2024):
|
||||
|
||||

|
||||

|
||||
|
||||
## Technical composition
|
||||
|
||||
The 'edf_poc'-product should be as self-contained as possible.
|
||||
|
||||
Thus all parts coming from upstream repos should have a physical copy in this repo with a reference to the upstream repo. Therefore we need a mapping table from parts here to references in upstreams.
|
||||
|
||||
Alternative: Submodules
|
||||
|
||||
Proposal: The final product will be a export of the repo
|
||||
|
|
Loading…
Reference in a new issue