2026-02-27 Time FT Kickoff

[lavrovvalera]

Location

Online via zoom: link to the meeting

Participants

@lavrovvalera
@umaucher
@mikehaller
@FScholPer
@BlueXMarv3l
@BjoernAtBosch

Meeting Minutes

Feature Team Lead

• Mondays tech syncs
• Moderating and managing the release
• -> @lavrovvalera

Planning

• Which dashboard to use?
  • it is available here: https://github.com/orgs/eclipse-score/projects/32

PR merging/integrating

• merge the exisiting PRs and then consider others (?)
• requirements
  • how does each pitch cover the requirements
  • Do we need to adjust the requirements
• ASIL label
  • do we need ASIL-B?
• How the PRs could be integrated, more detailed analysis, more "detailed" table -> @mikehaller
• BMW code will be published till 02.03 in bmw score::time pitch inc_time#6
• need to decide the Apps APIs -> also need to consider the needed APIs (except the Now)
• we could consider the discusions from 4 comnponents (create tickets:
  • Define Applications API
  • Needs to consider several use cases. Need some sketch and so on.
  • Passive Now and Notifications API
  • Collect relevant use cases
• Need co consider all artifacts, which are needed for the certification
• shall everything be part of the 1.0 release or split somehow?

System architecture

• Is it QNX * Hyp?
  • QNX8
• Discussion with com
  • the ipc between host and guests -> @mikehaller
• HW support
  • Assumption of use
  • Customisations support
  • could we agree on QNX * Qualcomm?
    • There are many vendors, but Qualcomm wanted to support
  • Discuss with Qualcomm about their support -> @FScholPer
  • ECARX suggested to make the verification for stack on their reference platform. The VPN access to the HW could be provided to the team.

The repo template was updated

• the src -> score (or something)
• template needs to be updated
• need to consider this point as additional efforts (without immediate actions)

Agenda for 05.03

• Decide the next step integration based on the source code (merge strategy)
• Prepare the SAD sketch to visualize the components, responsibilities, which could be used as base to make decisions.
  • -> @lavrovvalera
• Cross-check the SCORE requirements towards tooling (bazel/docascode/license check/...)
  • cpp toolchain to be used
  • need to cross check, that the source code should be built with the new toolchains, so that SCORE env is being used and prepared