Rollout of Safety Sentinel

[LittleHuba]

• Integration of Safety Sentinel in overall documentation to be checked between @hoe-jo and @PiotrKorkus

[PiotrKorkus]

Meeting 25.06 15:00
@antonkri @MaximilianSoerenPollak @hoe-jo @LittleHuba @PiotrKorkus

We have currently 2 worlds - docs-as-code and trlc. All modules in SCORE should support docs-as-code. TRLC is used internally by some components and there is need to find a way to integrate it for traceability with current docs-as-code.

TRLC and lobster have better integration with bazel than sphinx-needs.
Comm depends on baselibs and baselibs define AoU in sphinx-needs. That creates a problem in establishing traceability

Docs-as-code are generating needs_json which might be a common place where those 2 frameworks meet together.
The most important things are REQs and AoU - lets use them as PoC that should be work together.

Communication suggest to introduce dependable_element that will be used by sphinx-needs and will be a way to exchange information between Modules.
Also it needs to be taken care of second way of integration - other Modules also need to be able to use AoU from Communication in their documentation.

Some common element probably can be established - we need to find a common format. Let's start with dependable_element.

Path to consider during PoC: from baselibs to comm to some other module to ref_int. We need to define requirements what information need to be exchanged before starting PoC.

@antonkri will prepare some PoC next week.

---

@MaximilianSoerenPollak @hoe-jo @PiotrKorkus will meet together and define what kind of data is needed to be exchanged and how for docs-as-code and trlc / lobster work together.

REQ proposal:

1. Keep number of elements to build as low as possible. (proposed by @LittleHuba)