Persistency FT Meeting Minutes 2025

[joshualicht]

All official meetings will be documented in this thread (starting 2025-08-28 as agreed in #1629)
So if you subscribe here, you'll get summaries of the meetings you missed.

[joshualicht]

Weekly 2025-08-28

Participants

@Elsaka-Ahmed-JC
@joshualicht

Agenda

Pull Requests (no drafts)

Open

testing DDD #76 #74
Dcalavrezo test rep #31
kvs_cpp: Adapt to Module Folder Structure #76
impl: consistent instance params #87
gitlint: Use gitlint from score #96
testing: reimpl supported datatype CITs #97

Closed

fix get all keys function #82
formatting: remove trailing whitespace #85
impl: change flush_on_exit APIs #86
Add S-CORE devcontainer #88
fix string literal conversion #89
use mw log instead of cout #90
Add score_python_basics bazel MODULE #93
impl: use interior mut for flush_on_exit #94
impl: make IDs implement Copy trait #95

Meeting Minutes

• C++: Snake Case (persistency) vs Pascal Case (other Repos)
  -> Snake Case is coming from Rust Naming Convention
  -> Pascal Case is used in C++ Components
  Desicion to be taken in the next Meeting 2025-09-04

• C++: Mockable API for KVS:
  -> Problem regarding static open() method (refer to this fork branch: mock_api
  Proposal from @Elsaka-Ahmed-JC: Remove static from open functionality -> return shared pointer (also to prepare access dictionary of available/opened kvs objects)
  Ideas to be discussed in the next Meeting 2025-09-04

• C++: Detailed Design
  -> There should be a template for detailed design, which should be used for all components
  This should be addressed in Architecture Community

Open Points

• Avoid changing the API in both C++ and Rust without discussing in the FT Meeting. No merges should take place beforehand

[vbogdanb]

Weekly 2025-09-04

Participants

@joshualicht
@vbogdanb
@umaucher
@vinodreddy-g
@arkjedrz
@Ahmed-Elsaka-JC
@PandaeDo

Agenda

Pull Requests (no drafts)

Open

Meeting Minutes

• Decided to follow what fits best for each language related to naming convention:
  -> Snake Case for Rust
  -> Pascal Case for C++

• C++: Mockable API for KVS
  Will be solved when we change to having a pool of kvs instances, this will remove the open function and the loading of kvs will be done in the in the builder.
  Hiding the KVS public constructer will be required.

• C++: Detailed Design
  Template available https://eclipse-score.github.io/process_description/main/process_areas/implementation/guidance/implementation_guideline.html

Open Points

• Discussion related to the usage of flash_on_exit

[vbogdanb]

Weekly 2025-09-11

Participants

Agenda

• How should the "storage_mode" be abstracted from Builder API (regarding set permission for kvs file inc_mw_per#107)

Pull Requests (no drafts)

Open

• Flush_on_exit will be removed and flush function should be updated to return error/success
• Investigate providing storage backend to the builder and transition from one backend to another
• To be review impl: instance pool based on global state inc_mw_per#91 and aligned with update kvs build to avoid reopen opened instance. inc_mw_per#102