FEO Weekly 2025-11-18

[TomFleischmann]

Participants

@FScholPer
Jan Staschulat (ETAS)
Shourouk Ramzy (Valeo)
Ahmed (Schaeffller)
Yefeng Fan

Meeting minutes

• Collection of topics

• How to proceed with multiple application frameworks (as there was a decision to have multiples)

• How to continue risk mitigation around rust

• Integration scenarios and plans

• We made it into the 0.5 alpha! Big shout out thank you to @FScholPer from the FEO team for last minutes help!

Application framework alignments

• Joint alignment points (scheduling, general APIs, ..) would be wise as soon as these FTs have regular cadence and meetings
• Other domains may need similar features, yet with extensions or totally differ to be fit for their use case (Ahmed doing an analysis currently as well around use cases for motion & energy )
  FEO may fit to motion & energy
• Analysis by Ahmed shared after X-Mas

Rust

• Certain risk regarding Rust certification (used libs, ..)
• One path: Already use Ferrocene and ensure the Rust parts already have no compiler warnings;
  yet no other in the project tried this so far so potentially FEO can be the first to try and setup (need follow-up with @johannes-esr and as well
  FerrousSystem)

Integration of FEO into S-CORE

• FEO using currently iceoryx2, work to mw::com ongoing, as well log&trace being currently still independent from S-CORE (a bit like an island)
• Orchestrator as well available as a general S-CORE component but not used in FEO as it didn't provide benefits to FEO
  Orchestrator can be used by applications in general
• As well envisioned that FEO makes use of baselibs Rust

Reference boards:

• Brief discussion about reference boards and SoCs. Potentially using a SoC which allows certain elements maintained in S-CORE in open source.

Q: Use cases for all the application frameworks to guide users about APIs, languages, their interconnections viable combinations.
A: Need is clear but it get's more visible with a bigger application sample but we do not yet have a contribution for this.
Would be a good point to bring this to the architecture community workshop. (Doc extension: Use cases & guidelines for all the application frameworks)

Q: Is there a community meeting that discusses the "Orchestrator"
A: Good one to reach out and discuss would be @qor-lb (Lars)

[qor-lb]

@TomFleischmann, @pawelrutkaq is leading the orchestration ft in S-CORE, feel free to reach out to him in this regard.

[TomFleischmann]

[like] Fleischmann, Thomas reacted to your message:

…

________________________________ From: Lars Bauhofer ***@***.***> Sent: Tuesday, November 18, 2025 2:17:03 PM To: eclipse-score/score ***@***.***> Cc: Fleischmann, Thomas ***@***.***>; Mention ***@***.***> Subject: [External] Re: [eclipse-score/score] FEO Weekly 2025-11-18 (Discussion #2088) External email. Inspect before opening any links or attachments. @TomFleischmann<https://urldefense.com/v3/__https://github.com/TomFleischmann__;!!OrxsNty6D4my!9dgFW29imL_hMoBFWXi_Gjb2u_ZK7z0eO93sjl2GqqJJLrHTlw14qDTPc3M408RfJk8F7THkMXeQf7LwjVA8D7_JuYvgLM_4aQ$>, @pawelrutkaq<https://urldefense.com/v3/__https://github.com/pawelrutkaq__;!!OrxsNty6D4my!9dgFW29imL_hMoBFWXi_Gjb2u_ZK7z0eO93sjl2GqqJJLrHTlw14qDTPc3M408RfJk8F7THkMXeQf7LwjVA8D7_JuYudDgzVSw$> is leading the orchestration ft in S-CORE, feel free to reach out to him in this regard. — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/orgs/eclipse-score/discussions/2088*discussioncomment-15001715__;Iw!!OrxsNty6D4my!9dgFW29imL_hMoBFWXi_Gjb2u_ZK7z0eO93sjl2GqqJJLrHTlw14qDTPc3M408RfJk8F7THkMXeQf7LwjVA8D7_JuYs9e3is0g$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AP7D2ZPOVAFCRKMQPJMHDRT35MS57AVCNFSM6AAAAACMOPHBCGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMBQGE3TCNI__;!!OrxsNty6D4my!9dgFW29imL_hMoBFWXi_Gjb2u_ZK7z0eO93sjl2GqqJJLrHTlw14qDTPc3M408RfJk8F7THkMXeQf7LwjVA8D7_JuYucLvABgA$>. You are receiving this because you were mentioned.Message ID: ***@***.***>

________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security, AI-powered support capabilities, and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.

______________________________________________________________________________________ www.accenture.com

[pawelrutkaq]

Here is our rust certification tracking Rust certification (view)