Logging CFT Weekly [2026-08-18]

[rmaddikery]

Participants

Agenda & Meeting Minutes

• v0.9 topics

  • @arsibo generate a folder structure for the components log_frontend; log_backend; datarouter => folders shall be only add if a artifact for that folder is available
    - proposal have two components log and datarouter. Problem the units which are realizing the component log are located in the repo logging and baselibs @arsibo: organize a meeting with Roland to discus the topic. Send out invitation in slack
    11.08.2026: Meeting will take place 14:30-15:00, 11.08.2026
    Meeting Notes:
    Goal: Define where we should put safety documentation for mw/log interface since its functionality is split in two repositories (score_baselibs and score_logging)

    Option 1 (Preferred): One safety manual for mw/log
    Baselibs safety_manual could point to mw/log safety manual in score_logging

    Option 2: Separate safety manual for mw/log in score_baselibs and score_logging

    Option 3: Really move source code (all mw/log) to score_basleibs:
    Ruled out since this creates cyclic deps which is not intended.

    Option 4: Really move source code (all mw/log) to score_logging:
    Ruled out since score_basleibs and score_communication cannot log(use mw/log) anymore.

    Ideal to keep the documentation/artifacts close to code.

    NOTE:
    Create AoUs for mw/log in score_baselibs so that they can be forwarded.
    Create respective AoUs in score_logging that can be forwarded to users/integrators of additional backend.

    @aschemmel-tech volunteered to provide the first draft of the safety manual for mw/log as per Option 1.
    Draft PR: Add safety documents for logging logging#263

  04.08.2026: move content of log_rust to /score/mw/log/rust + adoptions due to process baselibs#390

  • @arsibo check with the process community about the usage of mw folder . mw has also a meaning of a stateful component (Markus Bechter / Andrej knows about that) => https://eclipse-score.github.io/score/main/contribute/general/folder.html will be updated . MW is used if it isn't only lib . It is used for runtimes. @rmaddikery please send out a PR to change https://eclipse-score.github.io/score/main/contribute/general/folder.html @anmittag has the latest info. regarding this and apprently its decided that "mw" can be used and the module structure will be updated (issue link to be added here)

  • 11.08.2026: Will be discussed in the process mention on 13.08.2026

  • 28.07.2026:

    • one Task per artifact is created LOG - Logging FT (view)
    • Epics
      • [feature logging] Work Products for S-CORE Release v0.9 logging#242
        • add parent Logging for S-CORE Release V0.9 #3017
      • [comp log_frontend] Work Products for S-CORE Release v0.9 logging#243
        • add parent Logging for S-CORE Release V0.9 #3017
        • add Add Detailed Design documents for mw/log and datarouter #3009
      • [comp log_backend] Work Products for S-CORE Release v0.9 logging#244
        • add parent Logging for S-CORE Release V0.9 #3017
        • add Add Detailed Design documents for mw/log and datarouter #3009
      • [comp datarouter] Work Products for S-CORE Release v0.9 logging#245
        • add parent Logging for S-CORE Release V0.9 #3017
        • add Add Detailed Design documents for mw/log and datarouter #3009
    • @rmaddikery :
      • Please add the task for v0.9 to the corresponding epic
      • there is an overlap with this v0.8 task. Proposal close them. We have also to clean up v0.8 planning.
        • https://github.com/eclipse-score/score/issues/3008
        • Add Detailed Design documents for mw/log and datarouter #3009
      • map Adding log frontend requirements baselibs#389 to [comp log_frontend] Component Requirements check/adapt logging#212
      • [feature logging] Feature Architecture completion logging#197 will handle process: DR-005 POC logging#52
    • Goals for 0.9
      • https://github.com/eclipse-score/score/milestones
      • https://eclipse-score.github.io/reference_integration/main/s_core_v_1/roadmap/pi2.html

• Code coverage

  • Decision: We want to have a common solution . We want to have a CFT logging proxy in that discussion. Murathan Güzel AVL will take over that task. Please check with the group in Slack for the current status. https://sdvworkinggroup.slack.com/archives/C0B8049QTNV
  • 14.07.2026: PR available but not merged Surface untested source files at 0% coverage in reports score_cpp_policies#9

• handling open PRs from the bot (e.g. Update dependency score_crates to v0.0.10 logging#167) @rmaddikery @anmittag tracking PRs already

  • if the check if green and it is a dev dependent it can be merged

• add the tracing feature to logging ?? => check with @hoppe-and-dreams + decision
  - Change the feature name from logging to log_and_trace
  - add tracing requirement
  - architecture API/component
  - NOTE: https://eclipse-score.github.io/.github/#naming

• feature requirements (TODO)

  • correct short name of https://eclipse-score.github.io/score/main/features/analysis-infra/logging/docs/requirements/mw-fr_logging_req.html#feat_req__log__err_handling_nonrec
  • check the content of the requirement https://eclipse-score.github.io/score/main/features/analysis-infra/logging/docs/requirements/mw-fr_logging_req.html#feat_req__log__err_handling_nonrec
  • remove valid_from: v2.0.0 feature requirement from the component requirements. Components will fulfill the feature requirements in future

follow up

• Bug list LOG - Logging FT (view)

Info

• AoB
  • https://sdvworkinggroup.slack.com/archives/C089XP2PGQ