Logging CFT Weekly [2025-02-18]

[arsibo]

Participants

Agenda & Meeting Minutes

1. CFT lead election
2. Decission Table
3. AI's from the workshop
   https://github.com/orgs/eclipse-score/discussions/375
4. Feedback Workshop
5. PR initial version of logging feature request #206

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

Meeting Minutes

1. Arvid Sievert will continue the CFT Lead

Criteria

Functional adherence to feature request

• ++ everything according to fr
• + partially fulfilling fr (subest of functionality)
• 0 fr needs to be implemented

Availability of source code

• ++ open source available under OSI compliant license
• + plan to be open source under OSI compliant license
• 0 open source available non OSI compliant license
• - not open sourced

Maturity (technical debt of code base): Is the implementation already safety certifiable?

• ++ implemented in a certifiable subset of C++ or Rust
• + refactoring needed but mostly using certifiable subset of C++ or Rust
• 0 written in QM or not according to project programming language

Adherence of available artifacts to score process expectations. Are all artifacts for a certification available in public?

• -- not available (no plan to close the gaps)
• - not open source but available (not planned to open source)
• 0 not available but plan to close gap exists
• + not open source but available and planned to be open source
• ++ available in open source and compliant with S-CORE process

Log & Trace

Criteria	mw::log	Log & Trace	MP Log
Functional adherence to feature request	++	++ covers also tracing	+
Availability of source code	++	++	+
Maturity (technical debt of code base): Is the implementation already safety certifiable?	++	0	++
Adherence of available artifacts to score process expectations. Are all artifacts for a certification available in public?	+	-- only artefacts from COVESA/dlt are availible	+

mw::log: https://github.com/eclipse-score/inc_mw_log/tree/bmw_logging

"D15: BMW log will serve as the implementation behind the logging frontend façade." from WS is accepted with respect to the decision table above

3. Next steps
   work on
   D16: Use the Rust log/defmt crate as the frontend façade for Rust.
   D17: Ensure that the C++ and Rust facades have the same "look and feel".
   transfer AI from ws to issues R: arsibo

• many different dimensions of the presentation mixture between different abstraction levels
• Agenda tracking/transparency could be improved
• improve technical setup => audio, digital whiteboard
• difficult to follow the discussion from remote => improve moderation of discussion
• build a common understanding about the terminology in advance

5. go ahead with pull request

6. Todo: present Milestones in the next meeting.