FEO Weekly 2025-06-03

[johannes-esr]

Participants

@johannes-esr
@ramceb
@vevmaki
@poeschel
@FelixMoelders
@Saumya-R
@hanky-qorix
@4og
@FScholPer

Agenda & Meeting Minutes

General

• Meeting next week is cancelled
• Feature Request for Record & Replay #1167 -> @johannes-esr to schedule meeting (@vinodreddy-g , @vevmaki , @armin-acn, @ramceb , @4og)

Review of Project Board

• FEO FT (view)
  • Epic: Create requirements for feature "FEO" #938
    • Create feature requirements for FEO #1081
      • Schedule Meeting on 1st of July, 2pm - 5pm (@johannes-esr, @armin-acn, @ramceb, @arsibo)
    • Create component requirements for FEO #1082
      • PR merged to score repository (Added FEO component requirements #1108), to be transferred to feo repository afterwards
      • To be reviewed after review/creation of Feature Requirements; @ramceb to prepare a set of Feature Requirements
  • Epic: Create architecture artifacts for feature "FEO" #941
    • Create feature architecture #1083
      • PR created, but closed without merging; Added FEO feature architecture #1109 -> PR will be reworked
    • Create component architecture #1084
      • to be done, based on Added FEO feature architecture #1109
  • Port FEO to new repository based on Module Template #1189
    • Currently dependent on implementation of Rust toolchain in module template repository
  • check which parts of std is used in the existing implementation. #1156
    • Current Approach: Document used std & core modules/crates in AoUs of FEO
    • Draft for AoUs: First draft of FEO safety manual, covering AoU wrt Rust std library. #1096
    • Status in Persistency?
  • FEO: Integration of Logging Feature #1073
    • Meeting scheduled on Thursday
  • FEO: Integration of Communication Feature #1072
    • BMW working on demo/sample applications to show the usage of mw::com --> currently on hold until these sample applications are published
    • Dependent on outcome of https://github.com/orgs/eclipse-score/discussions/1076
  • FEO: Supervision & Error Handling #1075
    • Error handling discussed -> @armin-acn will create PR with requirements regarding error handling
  • Specification: Consistent Logical Time Within Cause-Effect Cycles #1136
    • Will be part of Time Feature Request
  • Bugfix: Fix https://github.com/eclipse-score/inc_feo/security/code-scanning/1 #999, Bugfix: Fix https://github.com/eclipse-score/inc_feo/security/code-scanning/2 #998, Bugfix: Fix https://github.com/eclipse-score/inc_feo/security/code-scanning/3 #997, Bugfix: Fix https://github.com/eclipse-score/inc_feo/security/code-scanning/4 #996, Bugfix: Fix https://github.com/eclipse-score/inc_feo/security/dependabot/1 #995 --> @johannes-esr & @armin-acn to check how to fix
  • Propose configuration format for the activity chain including topic mapping #1162 -> to be checked with @ramceb
  • Define proposal for accessing time during record and replay #1160 -> no update available until now
  • Specification: Consistent Logical Time Within Cause-Effect Cycles #1136 -> under specification at @vevmaki
  • [WS AI] S-CORE/FEO reference system #673 -> to be checked with @ramceb if it can be closed

Planning of Milestones

• 2025-05-30 Functional Gap Analysis S-CORE v0.5 Completed / https://github.com/eclipse-score/score/milestone/11
• 2025-06-01 S-CORE v0.5 Release Candidate / https://github.com/eclipse-score/score/milestone/14
• 2025-10-01 S-CORE v0.5 Feature Complete / https://github.com/eclipse-score/score/milestone/19
• 2025-12-01 S-CORE v0.5 Certifiable / https://github.com/eclipse-score/score/milestone/23