Architecture Community [2025-01-27]

[qor-lb]

Participants

• Nico Hartmann @HartmannNico
• Arvid Sievert @arsibo
• Frank Scholter Peres @FScholPer
• Martin Thiede @mthiede-acn2
• Vinod Reddy Gopi Reddy @vinodreddy-g
• Lutz Niebergall @LuNieb
• Alexander Warg
• Lars Bauhofer @qor-lb

Agenda

1. Welcome Lutz Niebergall
   • Intended contributions & participants
2. Agenda F2F mid of Feb
   • Per feature full/half day (Architecture WG + Feature CFT):
     • Contribution pitch: Presentation of technical concepts with relation to the feature request
     • Feature grooming: Technical direction for S-CORE feature
   • Feature agenda
     • 11th Feb: FEO Application Framework (Architecture WG + FEO CFT)
     • 12th Feb: Communication (Architecture WG + IPC CFT)
     • 13th Feb first half: Logging (Architecture WG + Logging CFT)
     • 13th Feb second half: Persistency (Architecture WG + Persistency CFT)
     • (extension by 1 day so that every feature has a full day?)
3. Contributions & CFTs
   • Decision-basis for feature code base/contribution
   • Work instructions CFTs
     • Feature request agreed
       • PR to score repo docs/features/...
       • Consensus about vision & goals
     • Preparation contributions: every contribution as separate PR/branch in the respective incubation repo
4. Rust approach for S-CORE
   • Information about
     • Certified compiler/rust version
     • Supported OS/HW targets
     • Safety manuals/AoUs for the design of OSAL
     • Programming guidelines and coding rules (static analysis)
   • Link to Eclipse Rust SiG (see Proposal to form a Rust SiG within Eclipse SDV)

     Initial focus areas of the Rust Special Interest Group are:

     • Exchange experience and discuss opportunities and challenges around the adoption of Rust in the automotive and other safety-critical industries
     • Create and publish documents for practical guidance
     • Advise and promote Rust-based SDV projects
     • Promotion and potential future creation of open source tooling
     • Collaboration with the Rust Foundation on the topic of safety Rust
     • Recommendations for changes for the upstream Rust project

5. QNX/Target platforms compatibility

Meeting Minutes

to 1.

• contributions expected in IPC, Logging, Persistency
• Internal approval for open-source contribution; subsequently inclusion of participants in the CFTs

to 2.

• Contribution Pitch should include a relation to the feature request
• Half day is potentially to short for persistency - online follow-up if required
• Agenda & Layout agreed
• Time Schedule to be defined next week @qor-lb

to 3.

• No restrictions to contributions up front
• Additional information about maturity should be included in pitch (req, arch, safety analysis,...)
• potential inclusion of eCal @LuNieb
• All contributions for the features to be sent to @qor-lb; preparation of agenda per feature until next week
• Different approaches for existing open source projects & new open sourced contributions required?
  • Central place for all contributions required (inc repos)
  • Open to the contributor to select
    1. creating a PR in the inc repo for the contribution
    2. link an existing open source repo at the issue with the feature request
• Optional goal for contributions: should build and execute

to 4.

• Approach Ferrocene as S-CORE and include in next Architecture WG -> @FScholPer

to 5.

• Target/Reference Platform for S-CORE to be defined
  • HW: Is a physical platform even required? Dedicated HW is currently out of scope, concentration is on OS (no direct dependencies to BSP for 0.5)
  • OS: Linux & QNX 7.1/8.0
• access to QNX license to be discussed next weekly