Persistency CFT [2025-07-03, 2:30 - 4:00 pm]

[guysagnes]

Agenda

Participants

@guysagnes
@vbogdanb
@joshualicht
@umaucher
@vinodreddy-g
@Ahmed-Elsaka-JC

Organization

• Architecture Community F2F Workshop [2025-07-08 - 2025-07-10] #1247
  Architecture Community F2F Workshop [2025-07-08 - 2025-07-10]
  • https://github.com/orgs/eclipse-score/discussions/1247
    Propose to start a short meeting at 15.00

Team Feedback

• Pull Requests
  • https://github.com/eclipse-score/inc_mw_per/pulls?q=is%3Apr+is%3Aclosed

TL / Arch Meeting Feedback

• Persistency-KVS stay inside incubation repository until release of Process

• Versioning - Modules and APIs
  proposition to get unique version controlling API and Module

  • how to handle version of the shared object library - typical approach from Linux? @guysagnes
    https://eclipse-score.github.io/score/main/platform_management_plan/release_management.html (Feedback Schu, Markus)
    Bazel version start with version 0.1.0 → 0.1.0-alpha based on the sematic version

• Namespace for KVS Public Interfaces: score::mw::per namespace or score::per

  • The mw is related to the architecture high level @guysagnes
    proposition for kvs component name space: score::mw::pers:kvs

• Presentation of the proposition - mockable code → Alexander Lanin (SLACK)
  Start writing Rust API guidelines for S-CORE #1282
  Generated documentation: https://eclipse-score.github.io/score/pr-1282/contribute/development/rust/rust_api_design.html
  action: request for the C++ code MOCKABLE code definition

• Organization of the source repositories → Alexander Lanin (SLACK)
  Proposition - Common template update

Feedback

• Use of the https://eclipse-score.github.io/score/pr-1282/contribute/general/feature_flags.html

• Module is expected in context of safety element out of context -

  • it will dependent on the assumption of use if the same module is reported for different language.

• Module Folder Structure

  • https://eclipse-score.github.io/score/main/contribute/general/folder.html#module-folder-structure
    • in modules are defined as SeooC -> separated modules are expected
    • @vinodreddy-g contact process to allow identification of handling of rust/C++ and dependency.
    • @guysagnes to be reflected to TL
    • @vinodreddy-g alignment about the structure https://eclipse-score.github.io/score/main/contribute/general/folder.html#module-folder-structure with @dan

Report summary

Overview report of the Persistence FT: https://github.com/eclipse-score/inc_mw_per/pulls

• Common KVS incubation repository -
  • KVS Rust
  • KVS C++
  • KVS Tool
• Overview (progress)
  • Persistency FT (view)

Dependency (Open)

• Gaps feedback

• Architecture alignment with identification of the dependencies

  • planned 2025.cw29 - 17.08.2025 14:30

• Next step allow deployment under QNX C++ (and Rust)

---

Cross CFT

Architecture

Open actions

• Requirement related safety qualification level (QM / ASIL_B) started @sbachmann-qorix (Pilot)

Meeting Minutes

Related Persistency CFT Board:
Persistency FT

code delivery / documentation update

• https://github.com/eclipse-score/inc_mw_per/pulls
• https://github.com/eclipse-score/score/pulls

[umaucher]

sorry for the short notice update to the release / bazel registry topic:

• Preparation PR: MODULE: Preparation for registry release inc_mw_per#24
  --> https://github.com/eclipse-score/inc_mw_per/releases
  ---> score_persistency: Add module with metadata and initial Bazel files bazel_registry#68