TL workshop: planning

[antonkri]

Introduction

The goal of the workshop was to identify most important short-term topics, that should be ideally finished till 01.09.2025.

Must-have cross functional

Build Toolchain (Maximilian Pollak, @dcalavrezo-qorix, @nicu1989 , Nikola Radakovic, Alexander Lanin)

Prio: 1

• Prio 1.a
  • Mono repo or multiple repo approach needs to run smoothly
  • Pros & Cons of both approaches should be collected and a preferred solution should be proposed. First draft: till 12.07.2025, final solution: till 19.07.2025
• Prio 1.b
  • Compilation of every C++ component with GCC compiler should run in CI pipeline for every commit in main branch and/or nightly. The execution should be successfull.
  • Compilation of every C++ component with QCC compiler should run in CI pipeline for every commit in main branch and/or nightly. The execution should be successfull.
  • Define compiler flags for QCC/GCC (looks like Jochen Hoenle already has a proposal)
• Prio 1.c
  • Execution of unit-tests for every C++ component with GCC compiler should run in CI pipeline for every commit in main branch and/or nightly. The execution should be successfull. Code Coverage should be reported.

All other activities in doc-as-code are set on hold till further notice.

Reference integration (Sameer, Lukasz Tekieli, Xinquan Zhang, Mark Schmitt)

Prio: 2

• Prio: 2.a
  • Found and staff the integration team till 01.08.2025
• Prio: 2.b
  • Reference QNX image runs in Qemu x86_64 and wir can ping it over ssh
• Prio: 2.c
  • Reference Linux image runs in Qemu x86_64 and wir can ping it over ssh.

Detailed Design ( Philip Partsch, @vinodreddy-g, @dcalavrezo-qorix, ESR, Jochen Hoenle)

Prio: 3

• Prio 3.a

  • Detailed Design tooling should be ready for C++
  • Documentation should be provided how to link Detailed Design elements to C/C++ source code or unit-tests

• Prio 3.b

  • Detailed Design tooling should be ready for Rust
  • Documentation should be provided how to link Detailed Design elements to Rust source code or unit-tests

• Reporting zwei Mal pro Woche: Montag und Donnerstag 10 Minuten, die Einladung muss von TLs kommen.

• Pro Topic ein Ticket, wo alle Themen als Sub-tickets oder Action Points aufgelistet sind.

• Alles muss in einem jeweiligen ReadMe.md beschrieben sein.

Feature Teams

• FTs should proceed the work on implementation of S-Core v0.5/v1.0 gaps and creation of Feature/Component Requirements/Architecture

Architecture Community

• Improve/finalize and merge Feature Requests for S-Core v1.0
• Prepare and communicate "Call for Contributions" e.g. over mailing list
• Creation of Feature Teams should be decided based on Contribution Pitch at the next software architecture workshop in September

TLs

• Prepare "Platform Management Plan"
  • How do we plan?
  • How do we release software?
  • ....

Process & Architecture Community

• name Platform Safety Manager
• define Platform Safety Concept (Platform Safety Manager + Arch Community)

Testing Community

• make ITF run based on ITF tests of LoLa component
• define Component Testing Framework

PMP

[odra]

Hello, this is Leonardo Rossetti from Red Hat. I would like to be added to the Reference Integration team due to #855.

[opajonk]

Hi all, I would also like to be involved in 2.a / 2.c. I guess we from Elektrobit can contribute something here.

[edgarcalvillo138-del]

Hola guapa 😘

[AlexanderLanin]

WG3: We already have a solution for detailed design aligned with process team, so please make sure to sync and not develop a different approach.

[edgarcalvillo138-del]

README.md

[edgarcalvillo138-del]

Bg