Infrastructure breakdown of Milestone 1

[AlexanderLanin]

Goals

• Process & Tooling for requirements & architecture is available (sphinx-needs incl. additional checks for verifying traceability/consistency).
• Process & Tooling for Detailed design, implementation & unit verification defined and implemented (e.g. spinx-test-reports).
• CI/CD is capable to automatically verify the consistency & traceability.
• Tooling for test coverage & static code analysis.

Prerequisites:

• Selection of tooling (e.g. static code analysis).

All MVP defined features (FEO, IPC, Logging, Common Libraries, Persistency) can be built in software module repositiories. Until then, the modules are handled within the incubation repositories.

Acceptance Criteria:

• All modules use a common repository template (build, CI, gitlint, README, ...); to be checked by operational whether Git submodule/bazel module can be used to avoid code duplication.
• All modules are built with bazel, (C++17: clang for x86 Linux with -Wall, -Wextra, -pedantic; Rust: rustc 1.83.0).
• Unit tests are built and run, also via GitHub Actions.
• No strict adherence to coding guidelines, but coding guidelines are available.
• How to guide for reference build & test environment.
• Result: every software module can be built inside of its repository. No common integration so far, no running image.

Tickets we want to complete to match milestone "Process & Tools enable Development"

See https://github.com/orgs/eclipse-score/projects/6/views/5?filterQuery=is%3Aissue+no%3Ais_parent+-status%3ADone+milestone%3A%22TEST%3A+Process+%26+Tools+enable+Development%22

Prerequisites:

• Selection of tooling (e.g. static code analysis, see C++: Prepare Decision: code analysis tool #244).

Explicitly out of scope / to be discussed

• coding guidelines -> process team or language-community -> Coding Guidelines and Static Code Analysis in Implementation Process #529
• detailed design enablement - as we do not know what is missing
• new tools, checks etc which will be requested by process team, as we cannot plan them at the moment
• python support is not required according to roadmap?! --> needed for tests
• licensing support via Dash -> later